Gary Kjos
garykjos at gmail.com
Tue Sep 9 15:14:47 CDT 2008
Evidently it's been doing this for a while. http://bytes.com/forum/thread197772.html References the same issue in Access 97. Table internal to database works and linked gives error you are experiencing. And here is another posting regardingthe same issue - version not identified. http://www.dbforums.com/archive/index.php/t-1211186.html Perhaps you could import into a temp table in the front end and then append from there to your linked backend table? This link implies that one o fyour field types may be defined incorrectly and it only cares when it's a linked table and not if it's a local table. http://bytes.com/forum/thread210094.html So perhaps if you verify that your table definitions all match the data correctly you can fix it? I personally usually import into a temp table with most fields defined as text and then append to my real table from there once I am relatively sure of the data being formatted correctly. Good luck! GK On 9/9/08, Serrano, John K <John.Serrano at dayzim.com> wrote: > I am getting a numeric field overflow error when I am importing a text > file into an access db. > > > > Originally, I had all the tables, forms, queries, and reports in one > access application and never got this error. > > Once I split out the access programs into two separate databases > utilizing one access application to store all of the data (tables) and > the other access application as a front end application. > > I linked the tables and tried importing the same file and received a > "Numeric Field Overflow" error. > > > > However when I merge the tables back into the access application I don't > get this message? > > Any ideas as to what is going on? > > > > John Serrano > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- Gary Kjos garykjos at gmail.com