CPGDeveloper
Board Regular
- Joined
- Oct 8, 2008
- Messages
- 190
I created and administer a Microsoft Access Application -- there are about a dozen users.
I created an accde file that i distributed to all the users to put on their respective desktops.
Every time I make an update, the application identifies that there is a new version available, and a batch script runs to simply copy and paste the new version onto their desktop, replacing the old one.
This has been working well until today.
The newest version is working on everyone's machine except one.
The main form has some simple command buttons that are navigation buttons (next record, last record, etc. -- programmed with embedded macros) -- for one particular user, and only this user, they don't work.
The changes I made were mostly cosmetic and had nothing to do with these buttons. Using the accdb version on his machine, I notice that if I go into the back-end first and then open the main form -- everything works fine. If I open it directly, however, I have the same issue. Again, this does not happen on anyone else's machine, using accde or accdb. Is there a setting here that I'm missing?
He is running Windows 10, 64-bit. Most of us also have the same set up -- there are a couple of us who have Windows 8. But again, nobody else has any issues.
I'm going to have him Log-in on someone else's machine and see how that goes, but in the meantime, any ideas on what else might be causing this? It's bizarre.
I created an accde file that i distributed to all the users to put on their respective desktops.
Every time I make an update, the application identifies that there is a new version available, and a batch script runs to simply copy and paste the new version onto their desktop, replacing the old one.
This has been working well until today.
The newest version is working on everyone's machine except one.
The main form has some simple command buttons that are navigation buttons (next record, last record, etc. -- programmed with embedded macros) -- for one particular user, and only this user, they don't work.
The changes I made were mostly cosmetic and had nothing to do with these buttons. Using the accdb version on his machine, I notice that if I go into the back-end first and then open the main form -- everything works fine. If I open it directly, however, I have the same issue. Again, this does not happen on anyone else's machine, using accde or accdb. Is there a setting here that I'm missing?
He is running Windows 10, 64-bit. Most of us also have the same set up -- there are a couple of us who have Windows 8. But again, nobody else has any issues.
I'm going to have him Log-in on someone else's machine and see how that goes, but in the meantime, any ideas on what else might be causing this? It's bizarre.
