Linked Table Manager button (package network option)

[pat_nospam]

Just curious what methods you have all employed for distributing a package with networking option. Once the MDE is packaged, is there a way to launch the linked table manager in a way so that it's inclusive to the program feel, i.e. without going to Access main program, within the runtime version. I'm interested to hear other's solutions to this issue, since end users will have various paths, drive letters, etc for networking options that would be difficult to predict.

TIA,

Pat

 

[pat_nospam]

Pat --

Sounds like that would be the best way to do it. After setting my fe.mde to link to tables via the Linked Table Manager, where is that code located to hard code a UNC link?

Also, do you run into problems giving a //server/path/ that people have to follow? Or do they just map a drive matching your //server.name/path.name?

Thanks again for the assist,

Pat

If the app is being distributed in my organization so that I know where the be db will be, I just use the UNC naming convention to reference it. That way it doesn't matter if the users even have a drive mapped to the be directory let alone require that they all map the same drive letter.

//server/directory path/be_db.mdb