Hi,
I have a bit of a head-scratcher. We have a front end/back end split database using an mde front end (Bob Larson's classic technique to make client updates). We've had it running for years over a novell network (about 40 users).
Suddenly yesterday, a message popped up when launching the app on some computers. It's a pretty standard error message: (all network connections are fine)
Of course as an mde file, I can't really do much debugging to narrow the problem down.
Here's some of the frustrating things I've tried/encountered so far:
- It's only happening on some machines, not others. 2 I have checked with the issue are both like mine: win7, Access 2010 64-bit.
- I have a command line for the mde file, it throws the error with or without the command line, so it's nothing there.
- On a machine with the error, I tried launching the mdb file with the same command line (except the file name of course) and it worked fine. It's only the mde file throwing the error.
- On that machine, I used the mdb to create the mde from there, and it still gave the error. I copied that mde back to my machine and it works fine there.
There have been no changes recently to any of these computers. The only thing I can think of is some win update broke something? But I updated my pc with the latest win patches yesterday and I'm fine.
:banghead:
Any suggestions?
I have a bit of a head-scratcher. We have a front end/back end split database using an mde front end (Bob Larson's classic technique to make client updates). We've had it running for years over a novell network (about 40 users).
Suddenly yesterday, a message popped up when launching the app on some computers. It's a pretty standard error message: (all network connections are fine)
Of course as an mde file, I can't really do much debugging to narrow the problem down.
Here's some of the frustrating things I've tried/encountered so far:
- It's only happening on some machines, not others. 2 I have checked with the issue are both like mine: win7, Access 2010 64-bit.
- I have a command line for the mde file, it throws the error with or without the command line, so it's nothing there.
- On a machine with the error, I tried launching the mdb file with the same command line (except the file name of course) and it worked fine. It's only the mde file throwing the error.
- On that machine, I used the mdb to create the mde from there, and it still gave the error. I copied that mde back to my machine and it works fine there.
There have been no changes recently to any of these computers. The only thing I can think of is some win update broke something? But I updated my pc with the latest win patches yesterday and I'm fine.
:banghead:
Any suggestions?
