![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello This question has probly been asked & answered before, so please forgive me in advance. I use a dbf file which has a general field in which I store photographs. These are stored separately in a .fpt file which has the same name as the database. I have noticed that apparently there is a 2 gigabyte limit on this file. If this limit is reached within the runtime exe profram, the program just does not add any more data - no error message id given. If trying to append data from within development mode, a message something like "no more disk space available" (not the exact words) is given, even though I have plenty of space on the hard drive. Is anyone aware of this problem and is there a work-around that doesn't involve upgrading VFP? Thanks Mark Nixon |
#3
| |||
| |||
|
|
What most people do is not use general fields. Use a text field to reference a filename and store your pictures as jpg's (or gifs, tiffs, png, whatever) Speeds up your database and will reduce your database size substantially On Tue, 16 May 2006 14:02:47 +0930, "Jack Jones" ajack100nospam (AT) hotmail (DOT) com wrote: Hello This question has probly been asked & answered before, so please forgive me in advance. I use a dbf file which has a general field in which I store photographs. These are stored separately in a .fpt file which has the same name as the database. I have noticed that apparently there is a 2 gigabyte limit on this file. If this limit is reached within the runtime exe profram, the program just does not add any more data - no error message id given. If trying to append data from within development mode, a message something like "no more disk space available" (not the exact words) is given, even though I have plenty of space on the hard drive. Is anyone aware of this problem and is there a work-around that doesn't involve upgrading VFP? Thanks Mark Nixon --- AntiSpam/harvest --- Remove X's to send email to me. |
#4
| |||
| |||
|
|
I had thought of that, but I am a compusively neat & tidy person and the thought of literally thousands of jpeg files hanging around my computer is somewhat daunting. I know that I can store them all in a separate directory and back them all up separately to my database files, but it seems somewhat messy. |
|
I guess that is the only other option then. It seems odd to me that VFP databases are supposed to be able to store an "unlimited" amount of records when that is clearly not the case. |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
what you can do to (if you don't want to use MSDE) is to have more than one table to strore your pictures with a parent table to use the right one for the right picture (if your pictures are numbered, une a table for pictures beginning with "0", one for "1", ....). In my humble opinion, pictures need a lot of space and you will reach one limit one day. Storing them in a FPT forces you to import them and then to export them to see them. Leaving them as JPG in a directory allows you to 'browse' them with another tool as Photoshop or even Explorer. I'll go this way ... -- J. MAURICE @Grenoble.France.Europe UFPRC - Foxil However, storing them in directory structures will give problems with |
![]() |
| Thread Tools | |
| Display Modes | |
| |