[AccessD] Corrupted mde

You could write him a script to execute in the MDB version of the FE (if he cannot send you the BE)

<Air Code/>
CONST CORRUPTDB = "\\Server\Folder\SOmeDb.MDE"
CONST NEWDB = "\\Server\Folder\NewDb.MDB"

Dim Db as DAO.Database
Dim TD as DAO.TableDef
Dim sSQL as String

Set Db = CurrentDb

For Each TD in Db.TableDefs
	If instr(TD.Connect,"Database=" & CORRUPTDB) > 0 then
		sSQL = "Select * from [" & TD.Name & "].* INTO [" & TD.Name & "] IN '" & NEWDB & "' FROM [" & TD.Name & "]'
		CurrentDb.Execute sSQL
	End If
Next TD

<Air Code/>

Lambert

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Thursday, April 11, 2013 4:03 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Corrupted mde

I can see the data.  I suggested the make table query idea to him. 

First problem is that everything I do with this guy I do via GoToMeeting.
Slow, awkward, etc.  He recognizes that.  So he's going to try to get his customer's permission to send the back end to me.

2nd problem - maybe not a real problem - he's using A97 (the app has been in use for many years - originally developed in A97, never upgraded).  So when I create this new database it will be in 2000/2003 format and I'll have to convert it to 97 format.

3rd problem - for him, not for me - he doesn't have the BE in an mdb format.
Oh yes, he has the original mdb, but it's out of date because he's made lots of changes over the years to the mde through code.  Why mde back end?  To stop the users from altering the data directly. 

But if I do this exercise he'll have an up to date mdb back end. 

Thanks

Rocky


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert
Sent: Thursday, April 11, 2013 12:52 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Corrupted mde

You say you can *see* the BE tables via the FE links. Can you see the data?
If so then just build a bunch of MakeTable queries to dump the contents into a new BE - MDB (why would they want an MDE back end?).

e.g. SELECT SomeTable.* INTO SomeTable IN '\\Server\Share\Folder\NewBE.MDB'
FROM SomeTable;

Lambert

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Thursday, April 11, 2013 3:22 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Corrupted mde

Sorry for the double post but I didn't see this come through the first time.
 
R

  _____  

From: Rocky Smolin [mailto:rockysmolin at bchacc.com]
Sent: Thursday, April 11, 2013 11:01 AM
To: 'Access Developers discussion and problem solving'
Subject: Corrupted mde


Dear List:
 
I have a client who has a commercial application which is FE/BE, but the BE is an mde.
 
One of his users has a large BE which has become corrupted.  Cannot see the tables in the BE of course, but can see them through the FE links.
 
Compact and repair from the FE fails.  Decompile won't work .
 
Any suggestions on how to most quickly recover the data in the corrupted BE.
 
MTIA
 
Rocky Smolin
Beach Access Software
858-259-4334
www.bchacc.com <http://www.bchacc.com/> www.e-z-mrp.com <http://www.e-z-mrp.com/>
Skype: rocky.smolin
 

--
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