Janet Erbach
jerbach.access at gmail.com
Wed May 30 08:40:53 CDT 2007
Susan - Thanks for clarifying the Excel method for me. I'll try that one more time. And hello, Rocky - I did try decompile, about TWENTY times. No luck. And Arthur - since this particular *!$% application has more underwear to get bundled up in than Windows itself, importing all the 'clean' items into an empty database didn't really work either. I've got good backup copies of each form report, table, etc...but I can't actually run the app as a whole because it isn't properly registered. Sooooooooo - if Susan's shot in the dark doesn't work, I'm going to re-install the app from scratch and then import all my custom work from the 'fill the empty database' backup I've got. Thanks everyone - I'm glad to be in on this forum. Steven's been pestering me about it for a long time, and I finally got schmart and paid attention! Janet Erbach On 5/29/07, Rocky Smolin at Beach Access Software <rockysmolin at bchacc.com> wrote: > > Late to the party here but have you tried decompile? > > Rocky > > > > > > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Janet Erbach > Sent: Tuesday, May 29, 2007 12:13 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] How to repair corrupt database > > Susan - > > When you say 'open in Excel' do you mean just grab one table out of the > 50+ > that are in there? If so...I tried it, and no luck. I already tried > deleting the code attached to ReportX - and I can delete it, but then I > get > a 'save failed' error. Let me know if I misinterpreted your Excel method. > > Thanks! > > Janet > > > On 5/29/07, Susan Harkins <ssharkins at setel.com> wrote: > > > > This is going to sound really odd, but I have seen it work. Open it in > > Excel > > -- DO NOT save your mdb file as a Excel worksheet -- you'll totally > > destroy it. Just open it. Then, close it. I have absolutely no idea > > why it sometimes works, I just not that it does. Word of warning, it > > probably won't work, and you might want to make a copy before you do > > this. I've never seen opening an mdb in Excel hurt anything -- only if > > you save it as an xls file -- but I'd be over-cautious. > > > > You mentioned that in the new database, where you imported all the > > objects, that it's still complaining about missing variables, etc. > > Does ReportX's module have any code in it? Since you can't delete the > > module, try erasing all the code, then repair. Just a thought. > > > > Susan H. > > > > We use a third-party database in Access 2003 in to manage our customer > and > > sales data. This morning I was importing a report from a "storage" > > database, and accidentally selected an extra report that I did not want. > > When I noticed this extra report - call it reportX - was being > > imported, I hit 'cancel'. And now my database is corrupt. > > > > ReportX does NOT show up on the reports tab. It does, however, show > > up in the modules project window, and I can even view the code > > attached to it; I cannot delete it, though. If I try to 'trick' the > > app by creating a dummy 'ReportX' I get the message that 'ReportX' > > already exists. > > > > This is what I've tried so far: > > > > 1) Decompiled the app several times, then tried to recompile. I get > > repeated errors that 'ReportX you entered in either the property sheet > > or macro is misspelled or refers to a report that doesn't exist.' > > After 4 or five of those, I get 'Compile error: Module not found'. > > > > 2) Compact/repair the database - access crashes. > > > > 3) Running Jetcomp - error compacting database > > > > 4) Create an empty database - import everything. Although the import > > still complains about missing 'ReportX', it seems like I'm able to > > successfully import everything else. But I can't run the app because > > I get weird compile errors like 'variable not defined' or 'user > > defined type not defined'. This app is so dang convoluted to begin > > with that I don't even know where to look for the basis of these > > errors. It may even have to do with the fact that I have not properly > > registered this version of the app - the first time you run the > > installed app, it's supposed to detect your registration status and > > prompt you from there; I don't know if there is a 'manual' > > registration option. > > > > Is there anything else I can do to save the database? ANYTHING?? > > > > Thanks - > > > > Janet Erbach > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > Internal Virus Database is out-of-date. > > Checked by AVG Free Edition. > > Version: 7.5.467 / Virus Database: 269.7.0/804 - Release Date: > > 5/14/2007 > > 4:46 PM > > > > > > -- > > 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 > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.8.1/822 - Release Date: 5/28/2007 > 11:40 AM > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >