Copy mde file to each pc?

[jamest85]

Hi:

After migrate mdb database to sql server, I have created .mde and installed in each user's pc.

My question is: if I modify .mdb file later, and re-create a new .mde from my pc, can I copy the .mde to each user (replace the old one)? The main concern is: do you think those table links (tables from sql tables) will still work?(or I have to relink them manually?).

Thank you very much.

Jt

[Jim Doherty]

Hi:

After migrate mdb database to sql server, I have created .mde and installed in each user's pc.

My question is: if I modify .mdb file later, and re-create a new .mde from my pc, can I copy the .mde to each user (replace the old one)? The main concern is: do you think those table links (tables from sql tables) will still work?(or I have to relink them manually?).

Thank you very much.

Jt

What connection method are you using to connect to the sql server? windows integrated security or a user name and password stored in sql server itself? remember the connection string is stored in the connect property for each table. (have a look at the system table Msysobjects table to see what I mean)

In short ....if you are using 'windows integrated security' and your network user name has appropriate server permissions then you will be fine (provided your users machine has the necessary requirements namely the ODBC driver installed), otherwise if you are using a dedicated user name and password (stored on sql server) as part of the connection string string then merely copying that to another machine (and you would be doing that by copying over YOUR mde file if your connection method is not windows integrated security) would subvert the purpose of user identification as your network user would be logging into the server as YOU if I am being clear to you on this?

With regard to the compatibility of a users machine in relation to the ODBC capability, one technique you might wish to consider is having an unbound checkmark mounted on your main form somewhere that is set to zero as a default.

When your main form or database opens you always create the ODBC connection programmatically on the fly. If it is successful in creating it (ie a driver is present) you can then set the checkmark to true. This then gives you a little something to pursue as an indicator when some user or other says "I cannot connect from my machine" if when you ask them "is the checkmark zero?" you instantly know they have no sql server odbc driver installed on that machine. (which irritatingly does happen from time to time depending on how frugal your installations are)

Regards

Jim

[jamest85]

What connection method are you using to connect to the sql server? windows integrated security or a user name and password stored in sql server itself? remember the connection string is stored in the connect property for each table. (have a look at the system table Msysobjects table to see what I mean)

In short ....if you are using 'windows integrated security' and your network user name has appropriate server permissions then you will be fine (provided your users machine has the necessary requirements namely the ODBC driver installed), otherwise if you are using a dedicated user name and password (stored on sql server) as part of the connection string string then merely copying that to another machine (and you would be doing that by copying over YOUR mde file if your connection method is not windows integrated security) would subvert the purpose of user identification as your network user would be logging into the server as YOU if I am being clear to you on this?

With regard to the compatibility of a users machine in relation to the ODBC capability, one technique you might wish to consider is having an unbound checkmark mounted on your main form somewhere that is set to zero as a default.

When your main form or database opens you always create the ODBC connection programmatically on the fly. If it is successful in creating it (ie a driver is present) you can then set the checkmark to true. This then gives you a little something to pursue as an indicator when some user or other says "I cannot connect from my machine" if when you ask them "is the checkmark zero?" you instantly know they have no sql server odbc driver installed on that machine. (which irritatingly does happen from time to time depending on how frugal your installations are)

Regards

Jim

Hi: Jim
Thanks for your such detailed and professional response.

I am using window authentication, and I am using ODBC trusted connection, I have run the .mdb in each pc, and it's .mde also. Hopefully if I created a new .mde from my pc, I just copy and paste to each pc later on.

Thanks again.

jt

[Megalog]

Security issues aside, there was a similar question not long ago on MDE distribution that I answered here:

http://www.thescripts.com/forum/thread760986.html

Hope it gives you a few ideas!