By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,077 Members | 2,160 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,077 IT Pros & Developers. It's quick & easy.

Multiple Users

P: n/a
I have created a database with different forms/reports on it. It will be on a
server for 2 more people to access it. My question is.. Is there anything I
may need to do/know before I put it on the server for another user to use it?
Also, while the other user is using it, I will be adding more forms and
reports to the database. Will this conflict with the information the other
user is adding? Thanks.

--
Message posted via http://www.accessmonster.com

Apr 9 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Apr 9, 11:47 am, "stephendeloach via AccessMonster.com"
<u32891@uwewrote:
I have created a database with different forms/reports on it. It will be on a
server for 2 more people to access it. My question is.. Is there anything I
may need to do/know before I put it on the server for another user to use it?
Also, while the other user is using it, I will be adding more forms and
reports to the database. Will this conflict with the information the other
user is adding? Thanks.

--
Message posted viahttp://www.accessmonster.com
The way you have stated your intentions is sorta a no-no. You should
be putting only the data on the server. Every user should have their
own version of the forms (the front-end). Look up in help (I believe
it to be there) information on split databases. There is even a
wizard for it. You keep your code in the front-end (each user has
copy) and leave the data (tables) in the back-end and use links to the
backend.

-- Larry Engles

Apr 10 '07 #2

P: n/a
"stephendeloach via AccessMonster.com" <u32891@uwewrote:
>I have created a database with different forms/reports on it. It will be on a
server for 2 more people to access it. My question is.. Is there anything I
may need to do/know before I put it on the server for another user to use it?
Also, while the other user is using it, I will be adding more forms and
reports to the database. Will this conflict with the information the other
user is adding?
Access 2000 and newer won't allow you to share the database while you are developing
in it.

You want to split the MDB into a front end containing the queries, forms, reports,
macros and modules with just the tables and relationships. The FE is copied to each
network users computer. The FE MDB is linked to the tables in the back end MDB
which resides on a server. You make updates to the FE MDB and distribute them to
the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page at
http://www.granite.ab.ca/access/splitapp/ for more info. See the Auto FE Updater
downloads page http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. The utility also supports Terminal Server/Citrix quite nicely.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Apr 10 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.