formerTexan
Programmer
I was with a retro client who is still keeping a unified (BE & FE)Access database on their "server" with all 10-15 users accessing this over the local network. Access A2K and A2003 versions are variously installed.
While the database was in use, I opened up a VBA editor on the server copy to look for the source of a string length problem they were having. Closed things down without any changes.
Subsequently when the users opened up a "client side" copy, they received error messages about the loss of a library reference (unrecognized functios). I checked the reference library on server copy and all is in order.
They went with my on the spot suggestion of a seperate FE / BE arrangement and this seems to have bypassed the problem.
But I am curious as to what caused the orignal problem. ANy thoughts?
THanks,
Bill
While the database was in use, I opened up a VBA editor on the server copy to look for the source of a string length problem they were having. Closed things down without any changes.
Subsequently when the users opened up a "client side" copy, they received error messages about the loss of a library reference (unrecognized functios). I checked the reference library on server copy and all is in order.
They went with my on the spot suggestion of a seperate FE / BE arrangement and this seems to have bypassed the problem.
But I am curious as to what caused the orignal problem. ANy thoughts?
THanks,
Bill