I use Visual dBASE 5.7 or 5.5a or 5.0 (few differences).
Using memo or OLE fields I can store images which are stored in a .dbt file which becomes huge very soon and if something goes wrong with this file I will lose all images or I will have to reconstruct it again which needs much effort. I would like a programming or other solution or external program that will allow me
1) Best solution: to store the path of the image only (e.g. d:\images\myimage1.jpg) in a field of a record and to be able to view this image via a window in a form.
2) less attractive: to store an image in a record of a field of a table (type memo, OLE, Binary or even better a type specially designed to allow storing of jpg files) and the relative file to be stored in a directory of the hard disk solely (not many images in a single huge file).
Could you please help me, I love Visual dBASE and I don't want to use other newer data base programs. Thank you very much.
Using memo or OLE fields I can store images which are stored in a .dbt file which becomes huge very soon and if something goes wrong with this file I will lose all images or I will have to reconstruct it again which needs much effort. I would like a programming or other solution or external program that will allow me
1) Best solution: to store the path of the image only (e.g. d:\images\myimage1.jpg) in a field of a record and to be able to view this image via a window in a form.
2) less attractive: to store an image in a record of a field of a table (type memo, OLE, Binary or even better a type specially designed to allow storing of jpg files) and the relative file to be stored in a directory of the hard disk solely (not many images in a single huge file).
Could you please help me, I love Visual dBASE and I don't want to use other newer data base programs. Thank you very much.