Run Time error 3001

Bergja

Registered User.
Local time
Today, 16:52
Joined
Jul 11, 2008
Messages
17
I started my current project with little to know knowledge of MS Access or writing code with within MS Access so bare with me...

I have a split database, the tables are stored on a file server, the "front end" form is stored on each user's computer. I had my database doing exactly what I wanted from my computer. That is using one form to submit a record (henceforth known as Helpdesk), and use another to manage all submitted records(henceforth known as IMO). It was working perfectly for me. I copied Helpdesk to the individual machines of my users and then began testing it. I ran into a multi user problem where if I had IMO open no user could use Helpdesk to submit new records, or if one user had Helpdesk open and another tried to open it. Knowing nothing about multi user environments I did a little research and found a lot of data on the ADO recordset connection methods and what not. I made a backup of my DB and started the process of converting my DB from DAO to ADO to take advantage of this. after some trial and error, I decided to try some other methods first put and my DB back to DAO, now I get a run time error 3001 "Invalid Argument" when the following code runs:

Set rst = dbHelpdesk.OpenRecordset("Helpdesk", dbOpenDynaset, , dbSeeChanges)

So I guess I have two questions: How can I fix this error, and how can I set up my DB to allow multiple users to access the tables on the file server?
 
1. The code should be:
Set rst = dbHelpdesk.OpenRecordset("Helpdesk", dbOpenDynaset, dbSeeChanges)

you had an extra comma between dbOpenDynaset and dbSeeChanges

2. For multi user use you should have the database split (frontend/backend) with a copy of the frontend on EACH user's machine.

See here for more about splitting:
http://members.shaw.ca/AlbertKallal/Articles/split/index.htm

and see here for a tool that can enable auto updating of your frontends (so you never have to deploy updated frontends again. After the initial deployment the frontends will update themselves):
http://www.btabdevelopment.com/main/MyFreeAccessTools/tabid/78/Default.aspx
 
Re:

Thanks alot! What I had done was I split the database manually. Which doesnt seem to work well with a mutli user env, must have done something wrong, but I went back and use the database utility and it seems to be working fine, thanks again!
 

Users who are viewing this thread

Back
Top Bottom