access runtime and multi user DB

  • Thread starter Thread starter UsenetUser
  • Start date Start date
U

UsenetUser

How do can I deploy a multi user(split DB) Access 2007 DB along with
Access runtime to production sites where I have no knowledge of or
control over the target computers?

Is there a way to deploy both the front and back ends together using
the developer extensions?

Thank you.
 
Generally speaking, there are three kinds of people that respond to
Usenet questions:

1) Almost professional responders, like MVP's, who spend a great deal
of time fielding questions, and who take great pride in giving
accurate, appropriate and clear responses, rarely make mistakes, and
always apologize if they do.

2) People with a lot of personal experience with the technology
addressed in the group or forum, and also sufficiently experienced in
the Usenet and forums to have learned not to get in over their heads,
and to carefully read the question before posting a response.

They may even wait a day or two to be see if someone better qualified
posts one before posting their own if they are less than 100%
confident it is accurate and informative. These people have been
there, done that, and genuinely take pleasure helping others but are
smart enough to know they should be sure that their response is not
only accurate, but addresses the problem, or if they are not sure, to
qualify the response or ask for more info from the OP.

3) People for whatever reason - could be anything ranging from
enjoying putting someone else down, to boredom, to egomania, who never
give specific or targeted answers to the questions posed. Their
replies offer no assistance, do not provide information, guidance, or
links to *appropriate* sites for further assistance with the OP's
problem. They are generalized, vague, negative, offering absolutely no
assistance with the technical difficulty in question. They not only
provide no value, they lessen the OP's chance of getting a useful
response by padding out the thread.

Worst of all, just about invariably, they don't even carefully read
the OP's post before hammering away at the keyboard! They parse out a
few words, like 'shareware' and 'runtime', then make nonsensical
accusations about 'installing Access runtime as if it was shareware'
in response to a question about a shareware program distributed with
Access runtime.
 
I hope to do this in the near future. I have seen a small amount of
software written in Access using the runtime out in the market. Majority is
still written using other languages such as VB, .NET etc....

I personally bought the sage scripts for my upcoming Access2007 based
software. Haven't used them very much yet (just a few tests so far). They
make it easy to build and install package that includes your access files,
other dlls that need to be registered, documentation etc... and also handle
installing the runtime. Albert Kalall has a nice article on developer
extentions, and deciding on whether to go for the pricier more advanced
products to help with install scripts.
http://www.members.shaw.ca/AlbertKallal/RunTime/Index.html

Your split db is just two files that both go into the same install
directory. Instruct the user how to move the back-end to a shared network
drive if needed. Use linking code that will detect back-end in current
directory and relink tables (Allen Browne's) is my favorite.

I do worry about the runtime "messing up" the user's computer. Would love
to see one of the MVPs write about the details of what the Access2007
runtime can "mess up". For example if the user uses a previous version of
Access they might not be happy they installed your software. This "messing
up" problem should be fixed (because we should be able to build software and
distribute it to others without fears).

My two cents,
Mark
RPT Software
http://www.rptsoftware.com
 
Back
Top