From: gt3TakeThisAway@bredband.net   
      
   > There is also another reason to store as JPEG: The very same database is   
   > the source to some web-pages, and in that aspect there is a concern for   
   > speed an performance. With a high quality JPEG compression, there is very   
   > little degrading of the images. My hope was there could be integrated a   
   > third-party s/w for this into Paradox.   
      
   The graphic field type in a Paradox table will never store a JPG - it will   
   be converted to BMP.   
      
   I think that if you use the binary field type you will be able to store the   
   jpg file, but then you have the same problem as you describe below.   
      
   > You may have some points in storing graphics outside the database, and   
   > only storing the path. However, there are also some drawbacks doing this.   
   > Reports in Paradox draw images directly from the tables in a very nice   
   > way. With the files stored outside the database there will be a problem   
   > doing this. The same goes for showing images in a table grid on a form, I   
   > do not know how this can be obtained without the images beeing in a   
   > Paradox table.   
      
   I also only store the path to the file. For report purpose I load the images   
   into a temporary table. Performance might be an issue with a report with   
   many images but it has worked for me so far.   
      
   For forms I have never done it to a table frame but in a 1 x 1 MRO I use a   
   graphic object and use readfromfile which works OK.   
      
   Anders   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)