I have an app (Access front-end / SQL back-end) that has been compiled with
Access 2k into an .ade format. That file is loaded on a web server for users
to download to their individual workstations, and until recently, there have
been no issues. All users were intially using Office 2k, SP3 and are being
migrated to Office 2003, SP2. When the download occurs under the new version
of Office, the .ade extension is automatically converted to .mdb, leaving the
downloaded app with an improper extension and the user with a file that will
not execute. Once all users have been migrated (I do not control this), I
will compile the app with Access 2003 but I do not think this will solve this
issue.
Could this be a security control within Access 2003? If so, is there a way
to disengage? I am not an admin on the clients, so if it's a security policy
within Windows, I will have to instruct personnel to modify the extension
every time an update to the app is posted to the webserver. The .ade
extension is still a properly registered file type on the client.
Thanks for any suggestions....
|