Allowing two people to use one database 1

[maidenmac]

Hi Everyone,

I have a small problem. I have two users on a network and one database. They both have full permissions to this database and both can access it, however, not at the same time. It is Access 2000. I have looked through the FAQ's and in all honesty could not see something pertaining to this so I'm hoping that some wonderful person out there who knows more than I do could possibly help.

Look forward your help.

Cheers
MAC

 

[MakeItSo]

Best way (to allow a possible third user in future) would be to set up a small Frontend-db.
--> Create a new db
--> Link (not import!) all tables from the database you want to use
--> Copy this new db to both computers locally, e.g. under "C:\DB" or so.
Then you can use this db as if it was the original, with the exception that you can both use it aht the same time.

regards,
MakeItSo

Andreas Galambos
EDP / Technical Support Specialist
Bowne Global Solutions Wuppertal, Germany
(andreas.galambos@bowneglobal.de)
HP:

http://home.arcor.de/andygalambos

 

[smitchwitch]

I have several databases that I have split into a front-end and back-end. The back-end holds only the tables and the front end has all forms, reports, macros etc. This allows several users at the same time to access the data. The front-end sits on the users PC and the back-end on a server which can be accessed by all users.

Good luck,
Sonia

 

[maidenmac]

Thanks very much for all your help, will give it a go and see what happens.

Cheers
MAC

 

[Ed2020]

An Access database should support multi user access regardless of whether it is split or not.

Which MDB file the tables sit in makes no difference in this area at all.

Please do not feed the trolls.....

 

[smurf01]

Would anyone have any idea why when a user opens a form that is set for "data input" that the input boxes do not show, I understand that it may be a permissions problem but I have not set any special ones. I have created other DB's before that are shered on a network that do not give these same problems.

Regards

Paul

 

[MakeItSo]

Hi Paul,

maybe I'm not fully awake yet but what do you mean by form is set for "data input"?
If you mean that you have set the property "add data" to yes, then this means that you are using the form to add data only, and you will not be able to display existing records. Set this prop to no and check if the problem remains.
Which input boxes do not show? What are they: bound textboxes?
Give us some bones to gnaw on...

Andreas Galambos
EDP / Technical Support Specialist
Bowne Global Solutions Wuppertal, Germany
(andreas.galambos@bowneglobal.de)
HP:

http://home.arcor.de/andygalambos

 

[smurf01]

MakeItSo,
Sorry I gave you the wrong info, My form is set for Data Entry because this is where users will enter the new data. On the form in the details section I have six input boxes which can be combo boxes or text boxes. When the user opens the form the detail section is completely blank I think it is a permissions issue however, I have set up other DB's in the past in exactly the same way where I have split the DB and put the back end onto a server, with the users only seeing the front end and have never come across this problem.



Regards

Paul

 

[scubydiver]

What operating systems are on the users pcs? I had a similar problem with our Access database. I originally thought it was because it was upgraded so many times. Turned out the problem was the operating systems on the pc. One used Windows 97, the other 2000. I upgraded the Windows 97 and the sharing problem disappeared.

 

[smurf01]

Funny you should say that, I have been thinking that perhaps the reason is that I am running OS of XP Pro with Office 2000 whilst the users are running OS of Windows 2000 with Office 2000. This is the only thing that has changed recently. However I would not have thought that this would effect the permissions on the server where the databases reside ??

Regards

Paul

 

[CajunCenturion]

smurf01, I am surprised that a Tek-Tips veteran such as yourself did not start a new thread for your own question.

One additional item that you might want to check is if the form has a RecordlSource query, and if the RecordSet from that query is empty when you load the form. This can result in a blank screen. The following is an example of a work around for this issue.

Private Sub Form_Load()

   If (RecordsetIsEmpty(Me) = True) Then
      With Me.Recordset
         .AddNew
         .Fields(&quot;<field1>&quot;) = &quot;data1&quot;
         .Fields(&quot;<field2>&quot;) = &quot;data2&quot;
         .Update
      End With
   End If
End Sub

And the Function RecordSetIsEmpty is as follows, and should be placed in a module, and made public so that it may be called from other forms as well.

Public Function RecordsetIsEmpty(rFrm_Form As Form) As Boolean
    
   RecordsetIsEmpty = ((rFrm_Form.Recordset.BOF) And (rFrm_Form.Recordset.EOF))

End Function

Good Luck
--------------
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[smurf01]

CajunCenturion,
I would not call myself a tek-tips veteran although i do visit the site regularly to see if I can find solutions to my problems, and also help others if I am capable,

anyway
The forms I am calling are not querying records but are solely used for "inputting Data", the forms that do query records seem to load OK

Thanks for your response

Regards

Paul