John W. Colby
jcolby at ColbyConsulting.com
Mon Mar 31 11:08:56 CST 2003
In fact I was just appending the same data twice. I have a unique index on a combination of fields that should prevent the data from going in a second time. This was just a test of that index to make sure the data would not go in again. In fact though the user may end up importing several different files, one after another. The entire process is to ask the user to find the file, copy it to a specific file name in a specific directory so that the link works correctly, copy the original to a backup directory, then run the append queries to get the data out of the spreadsheets and into the table. From there a "all records in the previous" and "all records NOT in the previous" will be run for reporting purposes. It shouldn't matter what I am doing though. If it runs once, it should run a million times. It may very well come back and say "X records could not be appended..." because of the unique index, but it should NOT give me this "numeric overflow" error. According to help that means that "the data is too big for a btrieve field" or some such. IOW, one of those useless error messages. The fact that the data actually imports makes it even more suspicious. I just don't want to send out work that pops up useless error messages and has to be exited and reloaded in order to work. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Wortz, Charles Sent: Monday, March 31, 2003 11:11 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Access 97 - Numeric field overflow JC, You got me confused when you say "The append process works the first time it is run, then the second time, I get a Numeric Overflow." What are you doing the second time? Appending the same data to the same records, or appending some other data to some other records, or what? Charles Wortz Software Development Division Texas Education Agency 1701 N. Congress Ave Austin, TX 78701-1494 512-463-9493 CWortz at tea.state.tx.us -----Original Message----- From: John W. Colby [mailto:jcolby at ColbyConsulting.com] Sent: Monday 2003 Mar 31 10:01 To: AccessD Subject: [AccessD] Access 97 - Numeric field overflow Guys, It's been awhile since I have dealt with A97. I am doing an import of data from excel spreadsheets. The data in the spreadsheet is a dbl datatype, but is really a long int, i.e. no decimal points. I am linking the spreadsheet, whereupon I see that the datatype of the field is dbl. I build a base query that runs these fields through a clng() to convert them to long integers. I then append the data into a table. The append process works the first time it is run, then the second time, I get a Numeric Overflow. I get the overflow between the "you are about to..." warning and the "X records did not append..." error. In fact that second error never occurs. Once the error occurs, I have to shut down the db and re-open it, whereupon the query will run successfully one time, then the error again. I am at SP2 for A97, and I don't remember what the latest SP is for A97. Has anyone ever seen this problem? John W. Colby Colby Consulting www.ColbyConsulting.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com ---------------------------------------------------- Is email taking over your day? Manage your time with eMailBoss. Try it free! http://www.eMailBoss.com -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 3456 bytes Desc: not available URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030331/2a7d8df2/attachment-0001.bin>