|
-
Sep 10th, 2002, 02:31 AM
#1
Thread Starter
New Member
Standalone to Network
Hi,
I have a standalone exe and Database on my local machine at work, that I use as a Knowledge Base for myself.
Now the rest of the office wants to be able to read and update the information in the DB.
My question is, how do I go about coding this. I currently define my DB like this .
Option Explicit
Private Const dbname = "C:\program files\Knowledgebase\knowledgebase.mdb"
and open it like .
Set dbase = ws.OpenDatabase(dbname)
a Obviously I need to locate the directory on a network drive. What is the code I need to open the DB ?
b I need to think about record locking, How do I do that please, so people can update more than 1 record at a time. and how does the db know which is currently the last record, so it can get the next free one ?
Thanks.
Degz.
-
Sep 10th, 2002, 02:50 AM
#2
PowerPoster
A) Just change the path to a mapped network drive or shared resource!
i.e
Private Const dbname = "\\server\c\KB\knowledgebase.mdb"
B) i)Yes! But they can only Edit 1 record per time anyway. Perhaps i dont follow?
ii) rs.EOF
b
-
Sep 10th, 2002, 03:11 AM
#3
Thread Starter
New Member
Thanks,
Does the Database engine handle more than 1 person adding records then ?
And do I need to open the database in a different mode please ?
Degz
-
Sep 10th, 2002, 07:19 PM
#4
PowerPoster
Does the Database engine handle more than 1 person adding records then ?
I'm assuming by database engine you mean Jet, Access db's.
Yes mostly it will handle up to 255 concurrent users that can add\edit data. Though this is heavily affected by what record locks and cursors you use.
First my advice would be to change to ADO instead of that DAO code doesnt take to long say 1 hour depending on the amount of code.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|