Hello everyone, I'm developing a pb access to data access system, the development is to create a local MDB, in user DSN connection is established, the ODBC data source in the pb application open, enter
The SQLCA. DBMS="ODBC"
The SQLCA. The AutoCommit=False
The SQLCA. DBParm="ConnectString='DSN=the Inventory Management; UID=; The PWD=& lt; * * * * * * & gt; '
"
Connect using the sqlca;
Has not problem, development to the best, the function is complete, now the customer wants to multiple computers can access database,
I have been in the local area network (LAN) a computer name is Daisy - copy my MDB on the computer in the past, put in D disk, and modify permissions Settings folder sharing, also on the ODBC data source user DSN connection is established,
My neighbor online in your computer can open the computer of the MDB, prove that the network is no problem, what should I do next? How to modify the above program

CodePudding user response:

Suggested that the MDB into SQL database,

CodePudding user response:

In the DSN indicate the position of the database file, the file you want to share up, of course

CodePudding user response:

Excuse me the second floor, indicate the DSN program where position? Isn't every computer to have a DSN file

CodePudding user response:

Why use access database? In ASA database is also ok

CodePudding user response:

Access without concurrent processing control, file type desktop database if this direct access to cause problems, suggest using asa

CodePudding user response:

Still use to access

CodePudding user response:

Suggest the building directly into the SQL,, according to the requirement of the clients are estimated ACCESS is more and more not adapt to, if the current use ACCESS Shared ACCESS, later will always have a lot of problems, it is better to use SQL earlier

CodePudding user response:

Yes, use SQL, large use oracle
Ha ha

CodePudding user response:

Dbparm="ConnectString='Driver={Microsoft Access Driver (*. MDB, *. Accdb)}; DBQ=\ \ \ files. The computer name accdb ', CommitOnDisconnect='No', ConnectOption='SQL_DRIVER_CONNECT, SQL_DRIVER_NOPROMPT', TrimSpaces='Yes'
"Try this one

CodePudding user response:

Or without the DSN

CodePudding user response:

First you need to have a Shared path

CodePudding user response:

I checked the access can be handled within 10 concurrency control, the user just do into the delivery record, so I just choose the access to do it

CodePudding user response:

references 9 f xiajinxian response:

dbparm="ConnectString='Driver={Microsoft Access Driver (, *. *. MDB accdb)}; DBQ=\ \ \ files. The computer name accdb ', CommitOnDisconnect='No', ConnectOption='SQL_DRIVER_CONNECT, SQL_DRIVER_NOPROMPT', TrimSpaces='Yes'
"Try this

Can explain the role of parameters, whether affect the multi-user access

CodePudding user response:

Advice as early as possible migration, SQL, oracle is ok ~

CodePudding user response:

reference 13 floor CJLSWB reply:

references 9 f xiajinxian response:
Dbparm="ConnectString='Driver={Microsoft Access Driver (*. MDB, *. Accdb)}; DBQ=\ \ \ files. The computer name accdb ', CommitOnDisconnect='No', ConnectOption='SQL_DRIVER_CONNECT, SQL_DRIVER_NOPROMPT'...

I tried to multiple user
CommitOnDisconnect='No'//disconnected automatically submit
ConnectOption='SQL_DRIVER_CONNECT, SQL_DRIVER_NOPROMPT//connection fails not pop-up system odbc connection window
TrimSpaces='Yes'//remove the blank space on both sides of the field values