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

Multiple users using one form

P: n/a
Hi,

I have an Access database set up on a network drive that several users
can access. The database has many queries but just one main form. I
have designed a startup form where a user can select a query and the
main form will be opened using that query as the record source. Does
anyone know how this will behave when many users have the form open
with different record sources? Whenever a user selects a new query and
the record source is changed will this affect all users, or do they
all have their own instance of the form with its own properties? I
have thought about splitting the database to avoid this problem but
i'd prefer not to as security isn't an issue. I have tried testing
this and haven't found any problems but would like to know for sure if
the form will always behave correctly.

Thanks,

Michael
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
se*****@msn.com (Michael) wrote in
news:e7**************************@posting.google.c om:
Hi,

I have an Access database set up on a network drive that
several users can access. The database has many queries but
just one main form. I have designed a startup form where a
user can select a query and the main form will be opened using
that query as the record source. Does anyone know how this
will behave when many users have the form open with different
record sources? Whenever a user selects a new query and the
record source is changed will this affect all users, or do
they all have their own instance of the form with its own
properties? I have thought about splitting the database to
avoid this problem but i'd prefer not to as security isn't an
issue. I have tried testing this and haven't found any
problems but would like to know for sure if the form will
always behave correctly.

Thanks,

Michael


Michael, this is the best reason for splitting a database, even
more important than security. Split the data and the user
interface, give each user a copy and you won't have to worry about
changed recordsources, or changed queries.

Note that it probably will not be a provlem anyways, unless you
create temporary tables or querydefs (the definition of a query, as
opposed to the query itself)

Bob Q.

Nov 12 '05 #2

P: n/a
Bob Quintal <bq******@generation.net> wrote in message news:<a4******************************@news.terane ws.com>...
se*****@msn.com (Michael) wrote in
news:e7**************************@posting.google.c om:
Hi,

I have an Access database set up on a network drive that
several users can access. The database has many queries but
just one main form. I have designed a startup form where a
user can select a query and the main form will be opened using
that query as the record source. Does anyone know how this
will behave when many users have the form open with different
record sources? Whenever a user selects a new query and the
record source is changed will this affect all users, or do
they all have their own instance of the form with its own
properties? I have thought about splitting the database to
avoid this problem but i'd prefer not to as security isn't an
issue. I have tried testing this and haven't found any
problems but would like to know for sure if the form will
always behave correctly.

Thanks,

Michael


Michael, this is the best reason for splitting a database, even
more important than security. Split the data and the user
interface, give each user a copy and you won't have to worry about
changed recordsources, or changed queries.

Note that it probably will not be a provlem anyways, unless you
create temporary tables or querydefs (the definition of a query, as
opposed to the query itself)

Bob Q.


Thanks, I think I will split the database. Unfortunately I will
probably be making several changes to the user interface in the near
future and it's going to be a real pain to keep having to redistribute
it!
Nov 12 '05 #3

P: n/a

"Michael" <se*****@msn.com> wrote
Thanks, I think I will split the database.
Unfortunately I will probably be making
several changes to the user interface in
the near future and it's going to be a real
pain to keep having to redistribute it!


No, it certainly does not have to be "a pain"... see the topic on
"Versioning" at http://accdevel.tripod.com and look for MVP Tony Toews' Auto
FE Updater at http://www.granite.ab.ca.

Larry Linson
Microsoft Access MVP
Nov 12 '05 #4

P: n/a
NB
> FE Updater at http://www.granite.ab.ca.

Danny's solution for automated front-end updating:

http://www.databasejournal.com/featu...le.php/3286111

Having used both this and Tony's utility, I reckon Danny's approach is
better. Well, at least for me.

NB
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.