The app is for them to enter their "own" data. I figured in the future we
could offer an update as an MDE in whihc they would have to import the tables
or we could write a script that would do that?
Normally people distribute as two files: an MDE (which can be
placed on each workstation) and a linked MDB (which can be
placed on the network server). It's not the only way to do
it, but you need to think about what you are doing if you are
going to strike out on your own with your own approach :~)
If this is a small, non-networked, single-user application
then yes, distributing a single file now is a good idea, and
later you can provide upgrades by including a script to import
all the data.
(david)
> The app is for them to enter their "own" data. I figured in the future we
> could offer an update as an MDE in whihc they would have to import the
[quoted text clipped - 34 lines]
>> >>
>> >> (david)
MBoozer - 02 Dec 2005 05:40 GMT
Thanks Dave. I agree. But my distribution will be for network application
which means I should do be-fe. However, if I distribute as be-fe, then he
user has to do table linking and I'm not sure how that is done.
> Normally people distribute as two files: an MDE (which can be
> placed on each workstation) and a linked MDB (which can be
[quoted text clipped - 47 lines]
> >> >>
> >> >> (david)
david epsom dot com dot au - 09 Dec 2005 07:05 GMT
> user has to do table linking and I'm not sure how that is done.
Here are some examples:
How to relink back-end tables with the common dialog control in Access 2000
http://support.microsoft.com/?kbid=209862
Relink Access tables from code
http://www.mvps.org/access/tables/tbl0009.htm
> Thanks Dave. I agree. But my distribution will be for network application
> which means I should do be-fe. However, if I distribute as be-fe, then he
> user has to do table linking and I'm not sure how that is done.
>
>> Normally people distribute as two files: an MDE (which can be