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

Multi user - connection - error

P: n/a
ACCESS 97 : i have a table TblContacts with Name, adress, country,
phonenumber
I display these in a continous form on screen. I would like a multi-
user environment, so i split my database to front and end.

Question 1 : Is it not better to make a connection to open and close
like dim db as database, dim rs as recordset and so on.. if so how do
i populate my contious form. I searched the net but didn't find a
sample database

Question 2 : when i delete a record , user 2 gets after a few
seconds #name on his screen, how can i prevent that so he has the
updated records?

Tx, anyone, anywhere, anytime, anyhow, anyway

Mar 2 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On 2 Mar 2007 00:02:48 -0800, da*********@telenet.be wrote:

Q1: Not for regular forms. Just set the RecordSource and you should be
OK. Such code is OK when opening recordsets in code.

Q2: That's a normal side effect of multi-user apps. If you must, you
could add a Requery button users can click when they want to see
updated records.

-Tom.

>ACCESS 97 : i have a table TblContacts with Name, adress, country,
phonenumber
I display these in a continous form on screen. I would like a multi-
user environment, so i split my database to front and end.

Question 1 : Is it not better to make a connection to open and close
like dim db as database, dim rs as recordset and so on.. if so how do
i populate my contious form. I searched the net but didn't find a
sample database

Question 2 : when i delete a record , user 2 gets after a few
seconds #name on his screen, how can i prevent that so he has the
updated records?

Tx, anyone, anywhere, anytime, anyhow, anyway
Mar 3 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.