Access World Forums - what a wonderful place!
It's like having an Access encyclopedia!
Three years ago, I created an Access2000 database. It runs in .mdb, because we have no security issues in this situation, and I am often asked to "upgrade" by adding another feature. It's worked well until Access 2003 appeared on a few computers in this 22-computer network. On those computers, the buttons on the Switchboards that are 4 layers "down" from the Main board appear to "click" with the mouse on those Access2003 machines, but the underlying forms or reports do not run. All of the other features of the database appear to work fine.
The computers running Access2003 are XP machines that used to have Access (Office) 2000 on them, and the database worked fine then, so long as the Windows XP security against macros was turned off. After changing them to Office/Access2003, the problem appeared. Turning off the Office/Access2003 security against macros was required after installing the Office2003, but otherwise there are no other problems.
Any guru(s) out there have some good ideas about fixing this bizarreness?
It's like having an Access encyclopedia!
Three years ago, I created an Access2000 database. It runs in .mdb, because we have no security issues in this situation, and I am often asked to "upgrade" by adding another feature. It's worked well until Access 2003 appeared on a few computers in this 22-computer network. On those computers, the buttons on the Switchboards that are 4 layers "down" from the Main board appear to "click" with the mouse on those Access2003 machines, but the underlying forms or reports do not run. All of the other features of the database appear to work fine.
The computers running Access2003 are XP machines that used to have Access (Office) 2000 on them, and the database worked fine then, so long as the Windows XP security against macros was turned off. After changing them to Office/Access2003, the problem appeared. Turning off the Office/Access2003 security against macros was required after installing the Office2003, but otherwise there are no other problems.
Any guru(s) out there have some good ideas about fixing this bizarreness?
