G_Hosa_Phat
New member
- Local time
- Today, 16:31
- Joined
- May 15, 2008
- Messages
- 5
I have been looking over and over this issue multiple times and can't seem to get my head around it. I have a VB6 application with connection to an Access (2000/2003) database that does all SORTS of fun data manipulation. In fact, all of the same VB6 functions and subs are replicated to a number of different EXE's to handle the same type of data for multiple clients.
The problem is that for ONE of the EXE's/databases, whenever I first enter the database and look at some data, Access seems to believe that the record has been changed. Once it sees the change in the record (due to some coding in VB) will write a log of that record change to the appropriate table. Now, this would be all well and good if I DID actually make a change, but I had done nothing but view the data.
Here's the short version of the testing I've done so far...
Even more fun: We swapped the database for this customer's application with that for another customer for testing. At that point, we couldn't reproduce the problem no matter what we did.
That's not all: Based on that test, we tried running the problematic database using another customer's EXE. Here it's seeing changes to the database record when none are made.
FIGURE A
Executable 1 using Database 1 = Problem
Executable 2 using Database 2 = No Problem
Executable 1 using Database 2 = No Problem
Executable 2 using Database 1 = Problem
So, everything points to a problem in the database, not in the VB code. The only question is, where could such a problem be? The databases are virtually identical - a few different queries, some additional fields in certain databases while others have fewer fields. There are no macros or modules in any of the Access databases with which I've been working that might "accidentally" trigger. All of the field definitions appear to be exactly the same. I just can't find anywhere that might be causing this to happen.
Has anyone ever heard of such a thing? Any help in defining this a little better would be GREATLY appreciated. Thank you for your time.
The problem is that for ONE of the EXE's/databases, whenever I first enter the database and look at some data, Access seems to believe that the record has been changed. Once it sees the change in the record (due to some coding in VB) will write a log of that record change to the appropriate table. Now, this would be all well and good if I DID actually make a change, but I had done nothing but view the data.
Here's the short version of the testing I've done so far...
Even more fun: We swapped the database for this customer's application with that for another customer for testing. At that point, we couldn't reproduce the problem no matter what we did.
That's not all: Based on that test, we tried running the problematic database using another customer's EXE. Here it's seeing changes to the database record when none are made.
FIGURE A
Executable 1 using Database 1 = Problem
Executable 2 using Database 2 = No Problem
Executable 1 using Database 2 = No Problem
Executable 2 using Database 1 = Problem
So, everything points to a problem in the database, not in the VB code. The only question is, where could such a problem be? The databases are virtually identical - a few different queries, some additional fields in certain databases while others have fewer fields. There are no macros or modules in any of the Access databases with which I've been working that might "accidentally" trigger. All of the field definitions appear to be exactly the same. I just can't find anywhere that might be causing this to happen.
Has anyone ever heard of such a thing? Any help in defining this a little better would be GREATLY appreciated. Thank you for your time.
