Conversion made on Field type for liked tables

[crismroman]

Hi,

I have a problem related to filed type.
I have a linked table using ODBC. The table linked has improper field type: all numeric fields are linked as decimal. Because of this if I want to import the contens of this linked table in one new, the database has high dimension.

Please help me to find a place where I can set the field conversion for linked tables or to make Access to performe the better type conversion (if the field is integer on source table to be integer on linked table as well and so on).

Thanks !

[orange]

I don't understand this

...in one new, the database has high dimension.

You say ODBC linked tables ---> what type of table?? Oracle, MySQl????
What specific error are you receiving?

[crismroman]

There is no error received.
To have the whole picture:
1. I have a linked table using ODBC . The table is on AS400. Lets name this table Link_AS400
2. Using query over Link_AS400 I need to creat on MDB file TEST a new table X.
3. Because the fields type are "decimal" for Link_AS400 (instead of integer or long or the proper type) the MDB file TEST has a high dimension .

I cannot change the field type for Link_AS400. A workaround that I find is to creat field by field a table X and then to add records from Link_AS400.
My question is where I can set Access to make the proper conversion type for linked table.

Thank you,

[orange]

Do you have other Access--> ODBC-->AS400 examples?
What data types are involved in the links?
I don't have any AS400 experience, so can not comment from personal experience.

I did fiind thid link that may mean something to you
http://msaccesstips.com/2008/06/link...-as400-tables/

[crismroman]

Thank you for link.
What I saw related to table linked : all numeric fields are converted as decimal having the precision= maximum number of digits that the source field could have. Ex: the source field is designed to have maximum 3 digits then the filed is decimal having precision=3.
- in old version of Access (95 or 97) the field type was converted (for the linked table) to a proper type (the field type in example is integer for an older Access version).

Maybe this it is related with the driver involved in DSN creation... I don't have a clue..