Provide backend location on separate logon DB.
- From: "robert d via AccessMonster.com" <u6836@uwe>
- Date: Sat, 28 Jan 2006 19:27:48 GMT
I have a separate logon DB that a user opens when they want to logon to my
app. The logon DB puts together the shortcut for launching my workgroup
secured application.
On the logon DB, I would like to list the folder location of the back-end
files and allow the user to change it if required. When a user hits the 'OK'
button on the logon app, then in addition to creating the shortcut to the
secure front-end file, code will check to make sure that the back-end folder
location actually exists.
OK, this isn't hard to do.
But, if there is a new folder location for the back-end file, how do I pass
this string to the front-end file so that relinking can occur (I have all of
the relinking code working nicely).
Should I:
1) After launching the front-end from the logon DB, leave the logon DB open
and then close it from the front-end app after the front-end app has
retrieved the back-end location from a table in the logon DB?
Or is there a way to pass arguments when opening a DB in a similar fashion
that one passes OpenArgs between forms?
Also, please note that user machines are locked down so I can't make changes
to the registry.
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-externaldata/200601/1
.
- Follow-Ups:
- Re: Provide backend location on separate logon DB.
- From: Douglas J. Steele
- Re: Provide backend location on separate logon DB.
- Prev by Date: Re: Strip out Excel timestamp
- Next by Date: Re: Provide backend location on separate logon DB.
- Previous by thread: Re: To link or to import, that is the question (second post)
- Next by thread: Re: Provide backend location on separate logon DB.
- Index(es):