Heenan, Lambert
Lambert.Heenan at chartisinsurance.com
Fri Nov 16 10:45:36 CST 2012
Thanks for that Jim. I'll give that a go. Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Friday, November 16, 2012 10:58 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Access 2002/2003 Very strange behavior Hi Lambert: I had a similar set of issues a few years ago and found it all related to some corrupt set of functions/subroutines/forms/tables. The problem was solved by cutting out the contents of a module and dumping it into notepad. After all the modules/queries had been copied I opened up a blank MDB and dragged all the forms and reports across and then created new modules and populated them with the notepad contents. Each table was exported to a new table in the new MDB file. After that, the new MDB compiled and ran fine. I had no idea what exactly the problems were but believe it was cause by power issues. (I have also noticed the data moved to a SQL backend tends to be more resilient and less susceptible to data corruption especially in unstable power environments.) Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert Sent: Friday, November 16, 2012 7:23 AM To: accessd at databaseadvisors.com Subject: [AccessD] Access 2002/2003 Very strange behavior x-posted to Access-D and Access-L Post hurricane Sandy I have a group of users now running on Virtual Machines, and a smaller group who are operating remotely on their Blade computers that they have had for some years. A small sub-set of these users are having trouble opening applications they have been using for years. These are Access 2002/2003 applications, split into the usual Front End/Back End configuration. Most users are working fine, but there are some who get the message "This database is in an unrecognized format." when they try to launch the front end MDE file, and one user gets "The expression you entered has a function name that [App Name] can't find." One application is set up so each user has their own copy of the front end, and with another app. the (small) user group shares a single front end. I have found that for the first application, where users have their own copy, I was able to get them going by giving them a copy of the MDB file which the MDE is created from. They now see neither of those two messages. I have decompiled and rebuilt the MDE file, but still those two users cannot open it. (Little piece of detail, those two users happen to be remotely using a Blade computer, not a virtual machine. So they can run the MDB, but not the MDE. What's up with that? Then there is one user of the shared application who gets the "This database is in an unrecognized format." message, and yet all the other users have no trouble opening it. With that user if I get them to open the MDB version of the front end they simply get an hour glass for a longish time, and then Access comes back and says it has detected a corruption in the file, and the MDB is toast. All of this when nobody else is using the application. Does anyone have any brilliant ideas? Why would an MDB file work for some users and the corresponding MDE not? What might be causing the corruption of the other MDB file? Been struggling with this for the past two days! Any suggestions would be appreciated. Lambert -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com