TimK01
Technical User
- Jan 4, 2002
- 94
I have an application that was written in the dim distant past. It is currently running in Access 97. Way back then we used some macros to do some run time editing in a form. This has worked for years without a hitch.
We are now running on XP Pro, with Office 2003 (without Access). WE recently tried moving to a new server (2003) which failed and was backed out but left all XP machines with new user SID's and desktops etc, but all software still loaded.
Since then some machines fail when running the forms with macros others run quite happily. the error is usually "The functon you have entered cant be used in this expression". On machines with Access Runtime this takes the app down. On machines with full access running this is followed by an Action Failed window showing the Macro code ie UCASE, press the halt button and then the macro code runs.
The obvious solution is to take the macro's out of the forms, but the App is in the middle of a major revision and the changes would need to be retro fitted into that revision which i would like to avoid if i can find out what is happening and why it is machine dependant.
Its almost as if the internal code that runs the macros is failing but once you get over that everything works.
Does anyone have any ideas
Thanks
Tim
We are now running on XP Pro, with Office 2003 (without Access). WE recently tried moving to a new server (2003) which failed and was backed out but left all XP machines with new user SID's and desktops etc, but all software still loaded.
Since then some machines fail when running the forms with macros others run quite happily. the error is usually "The functon you have entered cant be used in this expression". On machines with Access Runtime this takes the app down. On machines with full access running this is followed by an Action Failed window showing the Macro code ie UCASE, press the halt button and then the macro code runs.
The obvious solution is to take the macro's out of the forms, but the App is in the middle of a major revision and the changes would need to be retro fitted into that revision which i would like to avoid if i can find out what is happening and why it is machine dependant.
Its almost as if the internal code that runs the macros is failing but once you get over that everything works.
Does anyone have any ideas
Thanks
Tim