<< Thanks, Larry. I will attempt a trial transition you suggested some time this week. I assume from your description that whenever I change the file (if it is stored outside of the database) the change will be automatic in RBASE as long as the file path does not change. Is that correct? If so, that eliminates one more step. When files are outside the database like that, how is the speed affected in reports, especially if I am printing a lot of drawings? >>
Yes, the link means that you're not storing a COPY of the file, only a reference to whatever's on disk with that filename. That also means, by the way, that someone can delete the file and you'll have a "dead link" — your program still points to the file but there's nothing there. To guard against that (if it's an issue) I suggest finetuning the network permissions on the document storage folder to only allow delete and create to the people who need it (everyone will need read, to see the documents). As for speed. If you change to the file link system then you'll have to change your reports to use a Variable Image control instead of the DB image. In your expression list you'll have to build the full name of the file (if you're not storing the full name already) and use a VARBIT variable to get the contents. The access to the file system will exact a speed penalty. On the other hand, you won't have to access the #4 file. You'll have to experiment to see what the actual effect is (please report back, so we can all learn from your experience). I'm not saying file linking is the correct method in all cases, and if these are images that you WANT to remove from the file system and that are really part of an integrated database record (as opposed, for instance, to WORD or PDF files that are separate entities) you might decide to store them in the database after all. -- Larry
