guys unsaon pag connect sa access nga database sa php
Check this out,
How to connect to MS Access | PHP and ODBC
PHP Database ODBCguys unsaon pag connect sa access nga database sa php
basic sample sa link bro,.first make an odbc connection to your ms acess database then sa imong php code refer to the link,. hope it will help,.,![]()
![]()
![]()
Mas maayo na solution: Stop using Access.
On a more serious, non-biased, non-hate mongering note, though. Use the old Google + PHP Manual combination. They go hand in hand and tends to be powerful resource in the PHP programmer's arsenal.
relative linkage: Here.
No need to extract, move or change database drivers. PHP can do it all.![]()
daghan mo occur nga problem if access imo gamiton in web based application if access gamiton My SQL, MS SQL or Postgre or Sybase simple to use ra....
i tried once using MSAccess, with my application with database system that connects thru network, way lami ang access ky hinay kaayo ang retrieving. Actually ms access is not design thru network, it is appliacble only in local if u want to maximize its perfomance. So i switch to MSSQL..if web ka mysql nindto, actually best buddy for php is mysql database system..![]()
@ ISDA_SA_BATO: bro nka try nka MSACCESS ang front end din MYSQL ang backend?
mao na akoa ghimo ron bt naa ko problem re sa image.. dli magpreview ang image nko. link ra makita sa image box nko sa front end na MSACCESS.
wla ko kasuway front-end msaccess bro,.mas maayo pa VB na lang ka..naa ra na sa google bro, ikaw na lang pangita,.,.![]()
![]()
![]()
How are you storing the image? It would be better to save the path (which I think you do) instead of storing the actual image data, and you don't need to worry about what data type should a backend have.
How are you displaying the image? What control are you using? Is the field bound?
Back to topic, I don't think there was a native PHP driver. You need to use ODBC (or OLEDB Jet) which someone already responded.
As to not using it, unfortunately Access is not very good in multi-user scenario. It also does not gracefully exit in its transactions therefore it is prone to corruption. I can't imagine a multi-threaded application connecting to Access, imagine a text file with 5 users simultaneously overwriting each other (I know, exaggeration). There maybe ways to handle this issue like creating multiple databases and handle the transaction management as part of your application BUT it is not worth the effort as that is what real database servers (MSSQL, MySQL, PostGre, etc.) are for
Similar Threads |
|