Working with MDE's

[Kodo]

Ok, There has got to be an easier way to do this. After devl'ing a db, I covert it to an MDE, but invariably, there's some glitches here and there. What is the best way to recreate the MDE without having to import the tables and recreate the relationships in the original database.

Every time I find a bug or want to modify a form or some code, I have to modify the original db and then import the new data from the MDE.

I thought "Maybe I should make an MDE front end and an MDB back end for the tables and link them" but I wasn't to kean on that idea because linking the tables in my environment where not everyone has the same drive mappings can be tricky.

How do you guys do it, what suggestions have you?

 

[MadMaxx]

If this is a multiuser db I strongly recommmend using a mdb backend. If not then no one will have to same data. And remember that if you don't use a backend for data and the database gets corrupt you lose all the data.

 

[Parker]

.

I thought "Maybe I should make an MDE front end and an MDB back end for the tables and link them" but I wasn't to kean on that idea because linking the tables in my environment where not everyone has the same drive mappings can be tricky.

This sounds like you are working on a network yes?

What OS's (both desktop and servers) are you running?

There are standards (or there used to be ) for namming network drives and everyone having the same maping.

It may be better to attack that problem first because no matter what you do if everyone has a different mapping for shared drives/folders, etc it will always cause problems anyway, if only from a support point of view.

 

[Kodo]

it is a multi-user, but the problem exists that users drive mappings to my file server are different. So correct me if I'm wrong here, but if I link a db to O:\fileserver\db\blah.mdb

and another user doesn't have an O: drive mappep, then they will not be able to use the linked db.. no?

 

[Kodo]

.

This sounds like you are working on a network yes?

What OS's (both desktop and servers) are you running?

There are standards (or there used to be ) for namming network drives and everyone having the same maping.

It may be better to attack that problem first because no matter what you do if everyone has a different mapping for shared drives/folders, etc it will always cause problems anyway, if only from a support point of view.

It's a bloody Novell network that I didn't set up. I can't change anything right now with mappings because we have a new Novell server being configured and I was informed by the Network "overseer" that I am not to change anything during the tree migration. Alas, I am under the gun here to build these db's .. rock and a hard place I tell ya. I might have to wait and split the db's when the server migration is complete. I have backups of all the dbs thankfully.. so if something gets fubarred I can restore it atleast.

When we get our new server, I will have to go over the login script with the "overseer"..

Thanks for your input!

 

[Parker]

it is a multi-user, but the problem exists that users drive mappings to my file server are different. So correct me if I'm wrong here, but if I link a db to O:\fileserver\db\blah.mdb
and another user doesn't have an O: drive mappep, then they will not be able to use the linked db.. no?

If your db is looking for 'O' then they would need to be able to either remap their drives or re link to a different source

Force your users to use the correct drive mappings. It’s not difficult (even in windows) that way the problem doesn’t exist.

If you have no contact with your users then include a destruction file with your FE telling them how to map the drive first. But you really should standardise drive mappings on any network otherwise it can be a nightmare.

I have seen a reference somewhere for allowing for searching for connections but that may be extremely messy and would not sort out other inherent problems that may occur. At best that would be an emergency, last resort patch. And, again, a nightmare to support

 

[Kodo]

If your db is looking for 'O' then they would need to be able to either remap their drives or re link to a different source

Force your users to use the correct drive mappings. It’s not difficult (even in windows) that way the problem doesn’t exist.

If you have no contact with your users then include a destruction file with your FE telling them how to map the drive first. But you really should standardise drive mappings on any network otherwise it can be a nightmare.

I have seen a reference somewhere for allowing for searching for connections but that may be extremely messy and would not sort out other inherent problems that may occur. At best that would be an emergency, last resort patch. And, again, a nightmare to support

it certainly has been a nightmare. the boob who set up this network didn't document a damn thing so I'm left trying to figure out who has what mappings and what drives are still available... se la vie I guess. Job security maybe lol.

 

[theprez]

This is how we do it for Applications we develop and distribute to customers. We create a front end and backend. We also have a routine where the customer can select the path of the backend tables. Once selected, we have a routine that links all the required tables. There is an activex control that allows the user to browse/explore their computer and selecte a file.

You need to use the common dialogue to query the user and link the tables. Look here

http://support.microsoft.com/default.aspx?scid=kb;en-us;181076&Product=acc

 

[Kodo]

BOOKMARKED!!

If I can get a common drive though, I might not have to use it. I've only got 15 more drive letters to check ..

 

[Pat Hartman]

Rather than specifying a drive, use the UNC name for the share -

//servername/path/dbname

To do this, just type the UNC name into the FileName box in the link dialog. This will make the link the same for everyone regardless of whether or not they have a drive mapped and what its letter might be.

 

[Kodo]

DOH! never thought to try a UNC to it..

*smacks self*

where's my corner.. lol