Frontend and Backend .MDE question. 2

[Lanie]

I have a frontend database and back end database. I need to make the frontend an .MDE for multiple users to access via a network. I have both the front and backend on the server in two different folders/directories. <br>
<br>
The backend tables are used by more than one frontend..<br>
<br>
If I make the frontend an .MDE do I have to make the backend and .MDE also?<br>
<br>
Thank you so much for any and all help.

 

[seaport]

It is not necessory to make the backend an .MDE. The Access database runs OK with frontend .MDE and backend .MDB.<br>
Since in most case there are only tables in the backend database, it does not make difference to make it an .MDE.<br>
<br>

 

[Lanie]

Thank you for your quick and timely help. Hope I can do the same for your sometime.

 

[nickdel40]

I have one question. Let's say you have some security settings for the backend part. Microsoft hints that you may want to turn the security levels off when you make an MDE...but can you add those securities back on after you made it an MDE?

 

[NickAtWork]

I am having trouble creating an MDE. I get the error &quot;Access was unable to create an MDE database&quot;. Accoding to the Microsoft Knowledgebase, this is an expected outcome if there is erroneous VBA code (which I do not have) or if the mdb you are trying to convert &quot;refers&quot; to another mdb. In the latter case, Microsoft advises that you make the related mdb into an mde. This seems to imply that the back-end must be an mde as well. But what if you don't have the choice of making all of the mdb's into mde's? In Access 97, I never ran into this problem. I had Developer in both 97 and 2000. Any ideas what's going on here? Thanks.
Nick Pettijohn

 

[mikehoot]

NickAtWork

I have recently been having a similar problem with one of my front-end db when trying to create an mde.

On the other hand, I have been creating and using mde files with linked tables with 100% reliablility for over 18 months using Access 97, and only recently came across this problem when trying to convert a new project.

The solution which worked for me (after a lot of trial and error!) was to create a blank db and import all objects, compile and save the new db, and I was then able to create the mde file. I dont't know why that worked, but it did!!

:-9

 

[NickAtWork]

I wonder if this is some kind of security patch gone wrong!

 

[Sameal]

Are you all compiling your VBA code from the VBA window before trying to turn the mdb into a mde?

It wasn't until I switched over to the VBA window and did a Compile there that I found a few programming errors in modules and reports that are rarely used. Thus they weren't surfacing until I tried to do a full compile. As soon as they were fixed with their appropriate CInt() casting calls, the database compiled just fine.

 

[NickAtWork]

I have verified my VBA code is compiled and without errors. The problem appears to be that the back-end is not an mde, and I cannot make it so, because it is part of a proprietary database program. This didn't used to be a be a problem with 97 and early 2000. Is this the result of a security patch, or is it a bug???

 

[NickAtWork]

There is a Microsoft Knowledgebase article that says if you have problems, make the &quot;assocoated databases&quot; into mde's.