Split before or after package/deploy?

[puzzled]

I have an Access 2000 database for a client with multiple users. I intend to
deploy using wizard in Office Developer, to deal with add-ins like flexgrid
& calendar. Question is should I split database into FE/BE and then create 2
packages (FE+add-ins) and (BE+.mdw), or do 1 package and split on site? Or
are there better options?

TIA

P.

 

[Wayne Morgan]

I would split it first and make sure everything is working as you want it to before
deploying. Once at the new site, you will simply have to relink the tables.

These articles may help with that.

http://www.mvps.org/access/tables/tbl0009.htm
http://www.mvps.org/access/tables/tbl0010.htm
http://www.mvps.org/access/tables/tbl0012.htm

 

[Ed Robichaud]

The most reliable and useful install strategy would be to split them first,
then distribute 2 install packs. The back-end MDB should wind up on a
server drive, and the front-ends should be installed on each work station -
linked to the BE at its specific location.
-Ed

 

[puzzled]

Wayne,

Thanks for the reply; I was concerned about some of the gyrations gone thru
in the files that you mentioned, to refresh links, etc. I have none of that
in my database at the moment. Do I need to do all that? How will I know if
it's not working properly? All I've done so far, in terms of testing is
split into FE/BE, moved BE to server, opened a couple of tables/ run a
couple of queries from FE and things seem OK ...

Rgds,

P

 

[Wayne Morgan]

No, you don't need to do all of that. What is in there is very generic and offers a lot of
flexibility. You can also do it manually (Tools|Database Utilities...|Linked Table
Manager) when you install the database, it just not a pretty that way. If you know what
the path to the back-end will be, you could simply have your startup form check for that
path and if it exists then check each table to see if it is a linked table. If it is a
linked table, then set its path to the new back-end path.