Hi all!
I have a VB app that stores records in an Access97 database. The users add records one by one, and when a counter reaches a preset limit (10), the app committs the transaction and zeroes the counter, in order to reduce network traffic.
My problem is that I've distributed the app to a colleague, and whereas HE can run it without a hitch, 'his' users can't. Instead they get error code 3246 - Op not supported in transactions. 'My' users have no problem, so I'm having trouble duplicating the problem. This is what we've tried so far:
1) Let user add records to table via the Access97 interface - No problem.
2) Give user full access rights to the disk and the database via the network - No difference.
3) Give user administrative rights to database - No difference.
It does appear to be an access right thang, since my buddy (sysadmin) can log into the same machine where the 'regular user' just failed, and succeed... But WHERE do I hack???
Cy
I have a VB app that stores records in an Access97 database. The users add records one by one, and when a counter reaches a preset limit (10), the app committs the transaction and zeroes the counter, in order to reduce network traffic.
My problem is that I've distributed the app to a colleague, and whereas HE can run it without a hitch, 'his' users can't. Instead they get error code 3246 - Op not supported in transactions. 'My' users have no problem, so I'm having trouble duplicating the problem. This is what we've tried so far:
1) Let user add records to table via the Access97 interface - No problem.
2) Give user full access rights to the disk and the database via the network - No difference.
3) Give user administrative rights to database - No difference.
It does appear to be an access right thang, since my buddy (sysadmin) can log into the same machine where the 'regular user' just failed, and succeed... But WHERE do I hack???
Cy
