Serious failure on OleDbConnection
Posted on 2005-03-24
I am having a serious failure using Access, with OldDbConnection. I have two program (both WinForms) which read and write to the same table. I am very careful to enclose all related code for both program in a try catch, and watch the Exceptions table like a hawk. But every so often it seems like a record disappears, and this problem effects any record. So I'm wondering if I'm overlooking something in the way I've designed this handshake.
One program produces the records by performing a write. The other program reads the record and deletes it to show the record's been consumed.
I log the preceding steps leading up to this problem, and see that both programs seem to be acting correctly. In other words, I see that the program producing the record actully produced it. And while other orders arrive into the log of the receiving program, sometime a single record (or sometimes two) simply never showed up on the other end.
I also found that I can compress and repair the Access table upon exit, and am now confident that file corruption is not the problem.
Does anyone have any idea about what could cause a record to disappear when no apparent exceptions are thrown? I'm really at a loss, especially since this is a show stopper for the whole project.
Thanks for the help.