.MDE file on NT Server

[RangerFan]

I have created a .MDE file that resides on an NT server.&nbsp;&nbsp;The users access this file via a shortcut on their desktops.<br>I periodically make changes to the original .MDB file and create a new .MDE.&nbsp;&nbsp;What I have noticed is that the users<br>then have to create a new shortcut to the .MDE.&nbsp;&nbsp;If they<br>don't, then the old version is still accessed.&nbsp;&nbsp;This does<br>not make sense to me.&nbsp;&nbsp;Perhaps I don't understand the true<br>nature of .MDE files.<br><br>Any help would be appreciated.<br><br>&nbsp;

 

[DougP]

Now keep in mind that when users add data to the .MDE it is not going in the .MDB<br>So when you create a new .MDE it is using the data from when ever the last time someone keyed anything into the .MDB. The way around this is creating a 3rd file called a Back end<br><br>Here are the steps to remedy everything.<br><br>First keep everybody out while you do this<br>Then make backup's <br>Next open the .MDB and Import the data (Tables) from the&nbsp;&nbsp;.MDE so it's current.<br>next Click &quot;Tools&quot; menu then &quot;Add-Ins&quot; then &quot;Database Splitter&quot; <br>follow the prompts <br>It will move the tables to a new database with the same name and _BE on the end.<br>Also when you click the tables TAB you will notice that all of the tables have a little black arrow in front of them (they are linked)<br>Next make your .MDE <br>so from now on the data the users are keying in is actually going into the _BE and when you manke a new .MDE it will have their latest changes<br><br>OK this is the way I do it.<br><br> <p>DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br> Ask me how Bar-codes can help you be more productive.