mde database (access 97/access2002)

Topic

New Reply

We have a mde database which has tables we need to access. Is there any way of doing this?

Reply | Quote

Replies

The tables in an MDE database are viewable. You may have to hold down the shift key as you open the database file?

Only forms, reports, modules etc can’t be accessed in an MDE (compiled) MS Access database.

Hope this helps.

Reply | Quote

The tables in an MDE database are viewable. You may have to hold down the shift key as you open the database file?

Only forms, reports, modules etc can’t be accessed in an MDE (compiled) MS Access database.

Hope this helps.

Reply | Quote

Jayden has already answered at least a part of your question, Pat. Is this a single file database? An mde on a back end isn’t much use, because as has been pointed out, the tables are accessible. Compiling an mdb into an mde just compiles the code. If you have further questions or need more help, please post back.

Reply | Quote

Yes it’s a single file database.

Can you access the tables in this single file database? I tried holding the shift key while opening the database but when it opens it shows no tables. I have checked the System and Hidden parameters but to no avail.

Reply | Quote

Unless the database has been protected somehow, you should be able to see any tables when you open the file, assuming that the tables are local to the mde. If you can’t see tables, then I can only assume that the allowbypasskeys property has been set to false and there is code operating to hide them. Do you get the defauolt menu when you hold down the shift key when opening the file?

Reply | Quote

>Do you get the defauolt menu when you hold down the shift key when opening the file?<
By the default menu do you mean the database window?

Reply | Quote

No, Charlotte meant the default menu bar at the top of the Access window (File, Edit, View, Insert, …). She wanted to know if Shift was enabled as bypass key. Since you can see the database window (even if you don’t see tables), it apparently is.

Reply | Quote

No, Charlotte meant the default menu bar at the top of the Access window (File, Edit, View, Insert, …). She wanted to know if Shift was enabled as bypass key. Since you can see the database window (even if you don’t see tables), it apparently is.

Reply | Quote

Patt,

Interesting thread. Regarding the MDE. Have the client create a new blank access database. Select File, Get External Data, Import and browse to the .MDE file. You should be able to see the tables even if the tables are linked to another database or hidden and import them. If you don’t see the tables in this process, then they either don’t exist or they have really secured the system well.

Any chance that user level security is in effect and the password being used does not grant full access to the tables?

As a test, I turned the shift bypass feature of one of my databases off and then created an .MDE. I could still import the tables out of the .MDE database using the process in the first paragraph.

Just my

Reply | Quote

On your first point, Hans has suggested this already.

There is no user level security.

A thought, how do you unhide tables that have been hidden?

Reply | Quote

Patt

Look in Tools..Options…View

Reply | Quote

Thanks John, I knew that one, however, I thought there was another way.

Reply | Quote

Try this:
– In a “normal” .mdb database, set a reference to the Microsoft DAO 3.n Object Library. The version is 3.51 – I think – for Access 97, 3.6 for Access 2000 and higher.
– Copy the following code into a standard module:

Sub ListTables()
Const strDatabase = “C:AccessTest.mde”
Dim dbs As DAO.Database
Dim tdf As DAO.TableDef
Set dbs = OpenDatabase(strDatabase)
For Each tdf In dbs.TableDefs
Debug.Print tdf.Name
Next tdf
Set tdf = Nothing
dbs.Close
Set dbs = Nothing
End Sub

– Substitute the correct path and filename for the .mde database.
– Run the code by clicking somewhere in it and pressing F5.
– ALL tables, including the system tables whose name begins with MSYS should be listed in the Immediate window.

What is the result?

Reply | Quote

That’s an excellent idea Hans.
Unfortunately the Client has not got back to me so I won’t bother you good people again on this topic until they do (get back to me that is).

Thank you all for your generous contributions and time, you are just fabulous.

Reply | Quote

That’s an excellent idea Hans.
Unfortunately the Client has not got back to me so I won’t bother you good people again on this topic until they do (get back to me that is).

Thank you all for your generous contributions and time, you are just fabulous.

Reply | Quote

Try this:
– In a “normal” .mdb database, set a reference to the Microsoft DAO 3.n Object Library. The version is 3.51 – I think – for Access 97, 3.6 for Access 2000 and higher.
– Copy the following code into a standard module:

Sub ListTables()
Const strDatabase = “C:AccessTest.mde”
Dim dbs As DAO.Database
Dim tdf As DAO.TableDef
Set dbs = OpenDatabase(strDatabase)
For Each tdf In dbs.TableDefs
Debug.Print tdf.Name
Next tdf
Set tdf = Nothing
dbs.Close
Set dbs = Nothing
End Sub

– Substitute the correct path and filename for the .mde database.
– Run the code by clicking somewhere in it and pressing F5.
– ALL tables, including the system tables whose name begins with MSYS should be listed in the Immediate window.

What is the result?

Reply | Quote

Application.SetOption “Show Hidden Objects”, True

Reply | Quote

Application.SetOption “Show Hidden Objects”, True

Reply | Quote

Thanks John, I knew that one, however, I thought there was another way.

Reply | Quote

I assumed from post 401092 higher up in this thread that Pat had already ticked the ‘Hidden objects’ and ‘System objects’ check boxes (the latter shouldn’t be necessary). If no user-level security has been applied, that should make all tables visible, even if their Hidden property had been set to Yes.

Reply | Quote

I assumed from post 401092 higher up in this thread that Pat had already ticked the ‘Hidden objects’ and ‘System objects’ check boxes (the latter shouldn’t be necessary). If no user-level security has been applied, that should make all tables visible, even if their Hidden property had been set to Yes.

Reply | Quote

Patt

Look in Tools..Options…View

Reply | Quote

Patt,

Any chance the MDE file was created using 97 and you are using either 2000 or 2002 to try to access it. As the code in the MDE is compiled, I think there may be compatibility problems if trying to get to the database using newer versions that may be preventing you to see the tables. If so, try opening the database using 97 to get to the tables. (Can you see any objects at all?)

My hidden file comment was answered by others.

Reply | Quote

Patt,

Any chance the MDE file was created using 97 and you are using either 2000 or 2002 to try to access it. As the code in the MDE is compiled, I think there may be compatibility problems if trying to get to the database using newer versions that may be preventing you to see the tables. If so, try opening the database using 97 to get to the tables. (Can you see any objects at all?)

My hidden file comment was answered by others.

Reply | Quote

On your first point, Hans has suggested this already.

There is no user level security.

A thought, how do you unhide tables that have been hidden?

Reply | Quote

Patt,

Interesting thread. Regarding the MDE. Have the client create a new blank access database. Select File, Get External Data, Import and browse to the .MDE file. You should be able to see the tables even if the tables are linked to another database or hidden and import them. If you don’t see the tables in this process, then they either don’t exist or they have really secured the system well.

Any chance that user level security is in effect and the password being used does not grant full access to the tables?

As a test, I turned the shift bypass feature of one of my databases off and then created an .MDE. I could still import the tables out of the .MDE database using the process in the first paragraph.

Just my

Reply | Quote

>Do you get the defauolt menu when you hold down the shift key when opening the file?<
By the default menu do you mean the database window?

Reply | Quote

Unless the database has been protected somehow, you should be able to see any tables when you open the file, assuming that the tables are local to the mde. If you can’t see tables, then I can only assume that the allowbypasskeys property has been set to false and there is code operating to hide them. Do you get the defauolt menu when you hold down the shift key when opening the file?

Reply | Quote

As Jayden and Charlotte have indicated, tables in an .mde database should be viewable, and you should be able to modify the design of the tables. There is no difference between .mdb databases and .mde databases in this respect. Have you tried changing the View option in the database window, for example to Details?

Reply | Quote

As you say the tables should viewable, however when you hit the Tables tab it shows no tables at all.

Are you saying that we should try and see the tables via the view set to details?

When we can see the tables can we link to these tables from another database?

Reply | Quote

In Large Icons view or Small Icons view, all tables might have been dragged out of the visible part of the database window. Tthe presence of scroll bars in the database window would be an indication of that. In List view or Details view, you should be able to see all tables.

> When we can see the tables can we link to these tables from another database?
Can you “see” the tables from another database now, if you select File | Get External Data | Link Tables?

Reply | Quote

>In Large Icons view or Small Icons view, all tables might have been dragged out of the visible part of the database window<
I will ring the client tomorrow and see if this is correct?

We cannot see the tables from another database? Although I didn't go thru File | Get External Data | Link Tables, I will again try this tomorrow.

Reply | Quote

>In Large Icons view or Small Icons view, all tables might have been dragged out of the visible part of the database window<
I will ring the client tomorrow and see if this is correct?

We cannot see the tables from another database? Although I didn't go thru File | Get External Data | Link Tables, I will again try this tomorrow.

Reply | Quote

In Large Icons view or Small Icons view, all tables might have been dragged out of the visible part of the database window. Tthe presence of scroll bars in the database window would be an indication of that. In List view or Details view, you should be able to see all tables.

> When we can see the tables can we link to these tables from another database?
Can you “see” the tables from another database now, if you select File | Get External Data | Link Tables?

Reply | Quote

As you say the tables should viewable, however when you hit the Tables tab it shows no tables at all.

Are you saying that we should try and see the tables via the view set to details?

When we can see the tables can we link to these tables from another database?

Reply | Quote

As Jayden and Charlotte have indicated, tables in an .mde database should be viewable, and you should be able to modify the design of the tables. There is no difference between .mdb databases and .mde databases in this respect. Have you tried changing the View option in the database window, for example to Details?

Reply | Quote

Yes it’s a single file database.

Can you access the tables in this single file database? I tried holding the shift key while opening the database but when it opens it shows no tables. I have checked the System and Hidden parameters but to no avail.

Reply | Quote

Jayden has already answered at least a part of your question, Pat. Is this a single file database? An mde on a back end isn’t much use, because as has been pointed out, the tables are accessible. Compiling an mdb into an mde just compiles the code. If you have further questions or need more help, please post back.

Reply | Quote