Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
PHP and MS ACCESS
- Thread starter bells
- Start date
MS Access is a pain to get working with PHP because PHP will not automatically terminate connections to the database.
Recommend using register_shutdown_function to kill off connections at the end of a page.
Also be aware that access only allows 5 concurrent users.
Go download mysql
--BB
Recommend using register_shutdown_function to kill off connections at the end of a page.
Also be aware that access only allows 5 concurrent users.
Go download mysql
--BB
- Thread starter
- #6
LordGarfield
IS-IT--Management
Well for those users it won't mather if it is mysql or acces becouse you probably create the web based user interface.
"save time from conversion from mysql to Access"
I think you would save more time if you do the conversion.
I do not know if you can get all sql statements out of Access (the full database in sql form)
if it can you simply can execute the statements on mysql and it will create all tables an inserts all values in it for you.
greetings
tank you,
(>" "<)
(='o'=)
-(,,)-(,,)------------------------------
LORD_GARFIELD
---------------------------------------
"save time from conversion from mysql to Access"
I think you would save more time if you do the conversion.
I do not know if you can get all sql statements out of Access (the full database in sql form)
if it can you simply can execute the statements on mysql and it will create all tables an inserts all values in it for you.
greetings
tank you,
(>" "<)
(='o'=)
-(,,)-(,,)------------------------------
LORD_GARFIELD
---------------------------------------
YoungManRiver
IS-IT--Management
A lot of mis-information here:
First there is no 5 user limit on Access, I don't know where you got that. We have an insurance company with over 300 concurrent users using a centralized Access DB, but you have to know how to define without exclusive rights and record locks.
When you are doing that there are no constraints on users, need to track them or kill them off. You just have to know how to code. If you are using the default kind of .ASP coding (by example) then get ready to get killed, don't work, won't work and will spend many hours, must more than converting to MySQL to correct. Normal coding mode for Access is single user with Exclusive rights to all tables and record locking turned on.
Some you turn off under tools the other is in the code with use of recordsets where you 1.) define, 2.) Set/Init, 3.) Open, 4.) Then close in single transaction with all values assigned to vars for DB offline processing. I'd give you an example except that's how I make my living.
About just dropping the SQL into MySQL and it doing it all for you, not true, close but not true. Code in Access and MySQL are first, slightly different syntax, not always seen but occasionally things go bump. Then you may have some tables to set up. Additionally if you are using relationships, whether coded or especially Access autolinked, indexing is a little more difficult with MySQL.
If you understand these difference then you will be on the right track to solving your problem.
First there is no 5 user limit on Access, I don't know where you got that. We have an insurance company with over 300 concurrent users using a centralized Access DB, but you have to know how to define without exclusive rights and record locks.
When you are doing that there are no constraints on users, need to track them or kill them off. You just have to know how to code. If you are using the default kind of .ASP coding (by example) then get ready to get killed, don't work, won't work and will spend many hours, must more than converting to MySQL to correct. Normal coding mode for Access is single user with Exclusive rights to all tables and record locking turned on.
Some you turn off under tools the other is in the code with use of recordsets where you 1.) define, 2.) Set/Init, 3.) Open, 4.) Then close in single transaction with all values assigned to vars for DB offline processing. I'd give you an example except that's how I make my living.
About just dropping the SQL into MySQL and it doing it all for you, not true, close but not true. Code in Access and MySQL are first, slightly different syntax, not always seen but occasionally things go bump. Then you may have some tables to set up. Additionally if you are using relationships, whether coded or especially Access autolinked, indexing is a little more difficult with MySQL.
If you understand these difference then you will be on the right track to solving your problem.
- Status