access as database php

[ISDA_SA_BATO]

---

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

nindot na nga algorithm bro..just get the path of the image.. i agree on that

[-_-]

nindot na nga algorithm bro..just get the path of the image.. i agree on that

OT: absolute path ang gamit ana?

[SYNCH]

OT: absolute path ang gamit ana?

OT: Relative path to prepare for future file system changes and you can have root folders set in the program or maybe tied to your business entity, etc. anyway you want it to. (This deserves a different thread btw).

[syst3m]

blob datatypes ang akong nasuwayan gamit bai for storing images in the database..

[budzprog]

nka suway ko bro na save na nko ang image sa database nko... ang akoa prob nalang kay dli mn ma preview ang image inig open nko sa akoa front end ang naa ddto kay link ra sa image...
sample... search ko sa akoa name: ma view pd ddto akoa image dli lng ang link..

[syst3m]

ang BLOB(Binary Large Object) datatypes bai ky d mana isave ang URL.. ang image man jd ang isave ana nya.. nakasulay ko bai nga nagstore ug nagretrieve ko sa image..