Splitting database to yet unknown destination.

[Jaazaniah]

I'm designing a small db for use by about 20 or so clerks. Because of
identified security issues, we've decided to split the data, and keep
the main structure out of reach of the clerks. Now, the thing is I'm
not on site and have no access to the type of file structure they will
be using to support this. Is there a way to set up db variables (in VB
or otherwise) so that a network location could be substituted in when
the db goes from test to live? I thought about setting it up as an
invisible label on all the forms they'll use, but that will leave a
lot of room for error when it goes live if the person doing the set up
misses a form. Any ideas?

[Susie DBA [MSFT]]

MDB doesn't work for that many users

you should just move to Access Data Projects

ADP is a much better _SOLUTION_

On Apr 23, 12:49 pm, Jaazaniah <[e-mail]:

I'm designing a small db for use by about 20 or so clerks. Because of
identified security issues, we've decided to split the data, and keep
the main structure out of reach of the clerks. Now, the thing is I'm
not on site and have no access to the type of file structure they will
be using to support this. Is there a way to set up db variables (in VB
or otherwise) so that a network location could be substituted in when
the db goes from test to live? I thought about setting it up as an
invisible label on all the forms they'll use, but that will leave a
lot of room for error when it goes live if the person doing the set up
misses a form. Any ideas?

[Jaazaniah]

On Apr 23, 4:21 pm, "Susie DBA [MSFT]" <[e-mail]:

MDB doesn't work for that many users

you should just move to Access Data Projects

ADP is a much better _SOLUTION_

On Apr 23, 12:49 pm, Jaazaniah <[e-mail]:

I'm designing a small db for use by about 20 or so clerks. Because of
identified security issues, we've decided to split the data, and keep
the main structure out of reach of the clerks. Now, the thing is I'm
not on site and have no access to the type of file structure they will
be using to support this. Is there a way to set up db variables (in VB
or otherwise) so that a network location could be substituted in when
the db goes from test to live? I thought about setting it up as an
invisible label on all the forms they'll use, but that will leave a
lot of room for error when it goes live if the person doing the set up
misses a form. Any ideas?

Scaling up to ADP is something new to me, and just checking out the
start of the wizard out of Access let me know how much I don't know
about larger databases. As I said in my OP, I have no idea of what
infrastructure they have on their network. They may not have an SQL
server, based on what snippets I've heard.

[John Welch]

You could store the back end path in a table in the front end.
Then you could write a vba funtion called GetBE_Path that reads that
value from the table. There is no place to tell Access to automatically
connect to that path, though - you'd have to write or find code that
does that. The Access Developer's Handbook has some good relinking code
in volume 2.

I don't agree that 20 users is too much for an mdb - it depends on how
well designed it is, whether they will all be using it simultaneously,,
how much they will be trying to access the same records, etc.

Susie DBA [MSFT] wrote:

MDB doesn't work for that many users

you should just move to Access Data Projects

ADP is a much better _SOLUTION_

On Apr 23, 12:49 pm, Jaazaniah <[e-mail]:

>I'm designing a small db for use by about 20 or so clerks. Because of
identified security issues, we've decided to split the data, and keep
the main structure out of reach of the clerks. Now, the thing is I'm
not on site and have no access to the type of file structure they will
be using to support this. Is there a way to set up db variables (in VB
or otherwise) so that a network location could be substituted in when
the db goes from test to live? I thought about setting it up as an
invisible label on all the forms they'll use, but that will leave a
lot of room for error when it goes live if the person doing the set up
misses a form. Any ideas?

[Albert D. Kallal]

Just about everyone of us has had to solve this problem.

the typical solution is pop up the file open browse dialog.

You can find this code here:
http://www.mvps.org/access/api/api0001.htm
You can then use the code here to re-link.
http://www.mvps.org/access/tables/tbl0009.htm

So, on start-up, your can try opening able, and if it fails, then you ask
the user if they want to link to the data file.

And, if the database is single user, and you want the database to work
regardless of what folder they place the application, then simply check for
the back end in the same folder, and re-link....
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

[Keith Wilby]

"Jaazaniah" <Ja****@gmail.comwrote in message
news:11**********************@e65g2000hsc.googlegr oups.com...

I'm designing a small db for use by about 20 or so clerks. Because of
identified security issues, we've decided to split the data, and keep
the main structure out of reach of the clerks. Now, the thing is I'm
not on site and have no access to the type of file structure they will
be using to support this. Is there a way to set up db variables (in VB
or otherwise) so that a network location could be substituted in when
the db goes from test to live? I thought about setting it up as an
invisible label on all the forms they'll use, but that will leave a
lot of room for error when it goes live if the person doing the set up
misses a form. Any ideas?

I use code to check a table entry for a path. If the path is either wrong
or non-existent then a browser window is displayed and the user can browse
to the BE file. Table links are then refreshed. If the wrong file is
chosen (the required tables don't exist in the file) then the user is
returned to the browser. If that's what you want then let me know and I'll
post the code.

Keith.
www.keithwilby.com