Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Access question
Message
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00326478
Message ID:
00326635
Views:
26
I don't understand a point here. You are developing an app for them, but they provided you with their Access MDB. You are either developing on their computer that had the only existing copy of the MDB or they gave you a copy of the MDB and deleted it off their computer. At such time you copied the MDB from the diskette and deleted the MDB from the diskette? I do not understand how this wound up with only 1 existing copy of their MDB file.

Was the MDB on a shared drive like a Novell drive where SALVAGE could be invoked to recover a deleted file? What's the story here?

>Well John, I'm starting to think you're right. I checked again with the client and they have no backup and it sounds like they did exactly what you said before sending the MDB to us, opened it in 2000 and did not convert, then tried to go back and forth between 2000 and 97 because they couldn't find any records. The strange thing to me is that the MDB file size still shows 30MB. Well, I'd say they're the ones who are "screwed"... awww heck, it was only their entire data store for 1999 in which they are suppose to create yearly reports for federal regulators!
>
>Thanks for the confirmation of what I expected anyway. Well, their shiny new VFP app will be nice and empty too! :)
>
>
>
>>I think it means your screwed, Mark. I have had some problems with MDBs opened in Access2000 if I did not explicitly convert them to 2000 from 97 when
> the Convert dialog popped up. I am fairly convinced that once you open up a MDB in Access2000, your best bet is to convert it and never go back to 97.
>
> >Thanks Jim for pointing that out to me. I tried the "Compact and Repair Database" menu option, which had not positive result. Then I tried the "Convert
> Database" option from the same menu, and during the "conversion" I got the following error:
> >
> >"There were compilation errors during the conversion or enabling of this database.
> >This might be due to old DAO syntax that is no longer supported."
> >
> >Which of course tells me nothing. Does this look familar to anyone?
Mark McCasland
Midlothian, TX USA
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform