Multiple versions of mdb

  • Thread starter Thread starter Ryan
  • Start date Start date
R

Ryan

I have an application I distribute to different companies.

It is the same application except for one form and table
which is specific to the company - reflecting their
specific use of the application.

Is there a smart way of handling this? Like having the
specific form in a mdb of its own and then link to the
shared part... or something in that direction?
 
Hi, Ryan.

Unless the special table contains confidential data, I can't see any reason
to have more than one backend file for all the tables. However, you should
split all the other database objects into a separate file. Each user can
then store the forms and report definitions on his local hard drive, and use
the network only for transfering data. Access supplies a utility to do
this--Tools, Database Utilities, Database Splitter.

Hope that helps.
Sprinks
 
Well - the problem is a little different.

The specific table can be handled with a dedicated .mdb
file with that table. The tricky part here is that the
front-end has a form that is specific to the customer.
I.e. customer1 and customer2 have different versions of
the front end. Only difference is this form "CustForm" -
everything else is the same - all other forms etc.

But instead of having Custform1, Custform2 etc. in the
front end, I would like to find a way of handling the
different versions of my front end - each with only the
applicable "CustForm" - but still reflecting the changes
made to the general part of the front end.

Does that make any sense?
 
Well - the problem is a little different.

The specific table can be handled with a dedicated .mdb
file with that table. The tricky part here is that the
front-end has a form that is specific to the customer.
I.e. customer1 and customer2 have different versions of
the front end. Only difference is this form "CustForm" -
everything else is the same - all other forms etc.

But instead of having Custform1, Custform2 etc. in the
front end, I would like to find a way of handling the
different versions of my front end - each with only the
applicable "CustForm" - but still reflecting the changes
made to the general part of the front end.
Click to expand...
if you don't use the custForm as a subform you can call it from a
second db (set a reference to it). The tricky part is:

in the second db you need a sub to call the frm and the recordsource
has to be in the second db or you have to work with recordsets as
recordsource
 
Back
Top