Has anyone experienced this kind of problem before?
I'm loading an Access table using input from a Delphi program and after a few thousand records Access starts to "miss-load" records.
Sounds screwy, but rows which were adjacent/contiguous in the input file end up (complete - ie no data loss) but separated, sometimes by hundreds of other record rows.
It's almost as if the Delphi program is feeding records faster than Access can deal with, with the result that the majority of records get written correctly but before the buffer has a chance to completely "flush" the next batch arrives...
Would the problem be solved/alleviated by using MSDE instead of the Jet engine?
Any ideas?
I'm loading an Access table using input from a Delphi program and after a few thousand records Access starts to "miss-load" records.
Sounds screwy, but rows which were adjacent/contiguous in the input file end up (complete - ie no data loss) but separated, sometimes by hundreds of other record rows.
It's almost as if the Delphi program is feeding records faster than Access can deal with, with the result that the majority of records get written correctly but before the buffer has a chance to completely "flush" the next batch arrives...
Would the problem be solved/alleviated by using MSDE instead of the Jet engine?
Any ideas?