VBA, access mde compilation failure

access mde compilation failure

Author	Message
- John of Arc #1 / 4	access mde compilation failure I have a database that runs fine until it is 'compiled' into an mde file. Often, it just beeps and stops, with a db1 left on the hard drive in who knows what state. Other times, it seems to compile successfully, but will scarcely run. It generates "memory....at adress...cannot be..." errors and crashes. I've found a couple of articles about mde bugs in access, but they suggest a large number of objects causing the troubles, and my datbase is not all that big: Q202304 Q177620 I wonder if compiling a database while it has linked tables does anything (like the infamous compaction fatigue problem that screws up the linked database when compiling its client. It does not appear that my database is corrupted. /decompile before creating the mde doesn't help either. Thanks for any suggestions.
Mon, 16 Sep 2002 03:00:00 GMT

Leah #2 / 4	access mde compilation failure Mr. Of Arc: Linked tables should not be the culprit, but just incase, you might want to eliminate the issue by importing them and seeing if the MDE will complete. Also, another way to check what's going on is to go into any code window and click Compile all Modules. This will point out any problems that MDE might be slipping up on. A third option is to create a new database, import all objects into it, and try again for the MDE. Sometimes a database gets so scrambled that not even compact and repair will fix it. If you're running Access 97 - get SR2. If you're running Access 2000 - you can try to get SR1, but it's time consuming, and some people had problems. I haven't, and put it on three PCs with varying brainsize and power. Hope something works. Later, Leah If thine enemy offend thee, give his child a drum. Quote: > I have a database that runs fine until it is 'compiled' into an mde file. > Often, it just beeps and stops, with a db1 left on the hard drive in who > knows what state. > Other times, it seems to compile successfully, but will scarcely run. It > generates "memory....at adress...cannot be..." errors and crashes. > I've found a couple of articles about mde bugs in access, but they suggest > a large number of objects causing the troubles, and my datbase is not all > that big: > Q202304 > Q177620 > I wonder if compiling a database while it has linked tables does anything > (like the infamous compaction fatigue problem that screws up the linked > database when compiling its client. > It does not appear that my database is corrupted. /decompile before > creating the mde doesn't help either. > Thanks for any suggestions.
Mon, 16 Sep 2002 03:00:00 GMT

- John of Arc #3 / 4	access mde compilation failure I'm using Access 2000 (which I've had more problems with than A97, even though VBA6 is so much better ). The database is completely compileable, runs fine as a non-compiled app. I find with Access 2000 that pretty much any database may become corrupted at any moment, for no apparent reason. Quote: > Mr. Of Arc: > Linked tables should not be the culprit, but just incase, you might want to > eliminate the issue by importing them and seeing if the MDE will complete. > Also, another way to check what's going on is to go into any code window and > click Compile all Modules. This will point out any problems that MDE might > be slipping up on. > A third option is to create a new database, import all objects into it, and > try again for the MDE. Sometimes a database gets so scrambled that not even > compact and repair will fix it. > If you're running Access 97 - get SR2. > If you're running Access 2000 - you can try to get SR1, but it's time > consuming, and some people had problems. I haven't, and put it on three PCs > with varying brainsize and power. > Hope something works. > Later, > Leah > If thine enemy offend thee, give his child a drum. > > I have a database that runs fine until it is 'compiled' into an mde file. > > Often, it just beeps and stops, with a db1 left on the hard drive in who > > knows what state. > > Other times, it seems to compile successfully, but will scarcely run. It > > generates "memory....at adress...cannot be..." errors and crashes. > > I've found a couple of articles about mde bugs in access, but they > suggest > > a large number of objects causing the troubles, and my datbase is not all > > that big: > > Q202304 > > Q177620 > > I wonder if compiling a database while it has linked tables does anything > > (like the infamous compaction fatigue problem that screws up the linked > > database when compiling its client. > > It does not appear that my database is corrupted. /decompile before > > creating the mde doesn't help either. > > Thanks for any suggestions.
Mon, 16 Sep 2002 03:00:00 GMT

Dev Ashis #4 / 4	access mde compilation failure As Leah has already pointed out, Linked Tables are likely not the reason behind the error. A compile to MDE affects only VBA objects, not Jet. Is your project in a fully compiled state before you attempt to convert to MDE? If not, then try decompiling a copy, and then issuing a "Compile and Save All Modules" before converting. -- Dev Ashish (http://www.mvps.org/access) : I have a database that runs fine until it is 'compiled' into an mde file. : Often, it just beeps and stops, with a db1 left on the hard drive in who : knows what state. : Other times, it seems to compile successfully, but will scarcely run. It : generates "memory....at adress...cannot be..." errors and crashes. : I've found a couple of articles about mde bugs in access, but they suggest : a large number of objects causing the troubles, and my datbase is not all : that big: : : Q202304 : Q177620 : : I wonder if compiling a database while it has linked tables does anything : (like the infamous compaction fatigue problem that screws up the linked : database when compiling its client. : : It does not appear that my database is corrupted. /decompile before : creating the mde doesn't help either. : : Thanks for any suggestions. : : : : : : :
Wed, 18 Sep 2002 03:00:00 GMT

Page 1 of 1

[ 4 post ]