Re: Export records from accdb?
- From: "Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx>
- Date: Sun, 23 Mar 2008 03:45:28 -0600
As the others mentioned there really is no specific changes to a accDB file
when you deploy to a runtime machine.
You can simply copy a accDB to any computer with a runtime version, or
fulltime version of access, and it will run and function.
If you need to issue a new update to your users, you can simply e-mail or
send them the file zipped up and they can place it on their desktop or
wherever and it will run with the runtime. I mention this because, often
enter some kinda misconception about the runtime system.
you can install the full version of MS access on the target computer, or the
runtime edition on the target computer. Once you've installed either
addition of MS access, any access database value copied and place on the
target computer will run (there is no special conceptual connection between
the runtime, and that particular database filed that was deployed with the
runtime).
What is significant with the runtime is much of the menu options and
importing/exporting features are not available to the end user via the
runtime edition.
So the data file itself can be mailed to you or whatever, and it's just a
regular access database file, and there are no specific changes to the
actual file itself. You can make changes to this file, and then sent it back
to the user.
What I would actually do in your case is actually send them a new front and
with your software updates and changes and modifications, and simply link it
to the existing data file that resides on their machines now (this means the
existing data file will become their back end). The only tricky part here is
you have to train or in ensure that users launch the new version of your
application, and not the old one with the data in it.
In a sense, I'm actually suggesting you split your database into two parts.
however since in your case since you already have the back end on the target
computer, you'll simply just be providing a new front end with your software
updates, but the data will remain in the old original database file. (if
you're not up to speed with split applications, then probably your best to
simply have them send the file to you for modifications, and then send it
back to them.
You should eventually adopt a split database. This allows you to issue new
updates to your software without concern overwriting their existing .
I explain the concept of a splt database here:
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
.
- Prev by Date: Re: Export records from accdb?
- Next by Date: Re: Excel
- Previous by thread: Re: Export records from accdb?
- Next by thread: Re: How to get and store pictures from a web camera?
- Index(es):
Relevant Pages
|
