Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 9 of 9 total |
Graphic field does not export |
Mon, Jul 24 2006 4:01 PM | Permanent Link |
"Ronald van der Pas" | Hi,
In a table I have a graphic field. In the Database Desktop I import a bitmap. That works fine and I can show the bitmap in my application. But if I try to "export" the bitmap in de Database Desktop then the resulting bitmap is empty. If I try this in code in my own application the result is the same. Has anyone seen this strange behaviour? I use V3. Greetings, Ronald van der Pas |
Mon, Jul 24 2006 11:02 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ronald,
<< In a table I have a graphic field. In the Database Desktop I import a bitmap. That works fine and I can show the bitmap in my application. But if I try to "export" the bitmap in de Database Desktop then the resulting bitmap is empty. If I try this in code in my own application the result is the same. Has anyone seen this strange behaviour? I use V3. >> I tried it here with 3.30 and it seems to work just fine. Are you possibly using an earlier version of 3.x ? -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Jul 25 2006 5:07 AM | Permanent Link |
"Ronald van der Pas" | Now I use version 3.26
Do you advice to upgade? "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht news:B5A3EB59-AFE6-4D05-97AE-F80CF792C6C6@news.elevatesoft.com... > Ronald, > > << In a table I have a graphic field. In the Database Desktop I import a > bitmap. That works fine and I can show the bitmap in my application. But > if I try to "export" the bitmap in de Database Desktop then the resulting > bitmap is empty. If I try this in code in my own application the result is > the same. Has anyone seen this strange behaviour? I use V3. >> > > I tried it here with 3.30 and it seems to work just fine. Are you > possibly using an earlier version of 3.x ? > > -- > Tim Young > Elevate Software > www.elevatesoft.com > > |
Wed, Jul 26 2006 12:21 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ronald,
<< Now I use version 3.26 Do you advice to upgade? >> Yes. Either that or just use the 3.30 DBSYS instead - it will work with the 3.26 tables okay. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Dec 25 2006 8:45 AM | Permanent Link |
Jim | Hi I have the same problem in that when saving (Exporting) a Graphic BMP field as a BMP, it does not open in Irfanview (Can't read file header ! Unknown file format). I tried this using the DBYSY utility that comes with DBISAM version 4.22 When testing this you need to use a utility other than DBSYS to try and read the EXPORTED BMP file. Can you please test and advise. Thanks Jim |
Wed, Dec 27 2006 5:39 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jim,
<< I have the same problem in that when saving (Exporting) a Graphic BMP field as a BMP, it does not open in Irfanview (Can't read file header ! Unknown file format). I tried this using the DBYSY utility that comes with DBISAM version 4.22 When testing this you need to use a utility other than DBSYS to try and read the EXPORTED BMP file. >> Where did the bitmap originally come from ? IOW, how was it originally added to the DBISAM table ? DBISAM performs no translation on the actual contents of the BLOB field, therefore what is exported will be exactly what was put in originally. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Dec 28 2006 7:35 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
Exactly what I can't remember but there's an itch at the back of my mind about this. Without looking at the code I presume DBSys uses a stream to save it to file? My memory says that in one app I had to use a stringlist to save to file otherwise the graphic wasn't recognised. I can't be anymore definite than that but I do remember a problem. Roy Lambert |
Mon, Jan 1 2007 7:05 AM | Permanent Link |
"Jim Meehan" | The Bitmap was added to the DBISAM table via the utility DBSYS that you
supply. I have tried this with several different BMP files ! The BLOB field has a "Data Type" of GRAPHIC. If you actually try to add a valid BMP to a DBISAM table field with a Data Type of GRAPHIC, using the DBSYS utility then try to save it via the EXPORT utility, the BMP is corrupted. Don't take my word for this. Try it yourself. It will only take you a couple of minutes, and you will see that there is indeed a problem. Regards, Jim "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:03B44A2C-6AB6-4687-B113-22887028434D@news.elevatesoft.com... > Jim, > > << I have the same problem in that when saving (Exporting) a Graphic BMP > field as a BMP, it does not open in Irfanview (Can't read file header ! > Unknown file format). > > I tried this using the DBYSY utility that comes with DBISAM version 4.22 > > When testing this you need to use a utility other than DBSYS to try and > read the EXPORTED BMP file. >> > > Where did the bitmap originally come from ? IOW, how was it originally > added to the DBISAM table ? DBISAM performs no translation on the actual > contents of the BLOB field, therefore what is exported will be exactly > what was put in originally. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > |
Tue, Jan 2 2007 1:59 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jim,
<< The Bitmap was added to the DBISAM table via the utility DBSYS that you supply. I have tried this with several different BMP files ! The BLOB field has a "Data Type" of GRAPHIC. If you actually try to add a valid BMP to a DBISAM table field with a Data Type of GRAPHIC, using the DBSYS utilitythen try to save it via the EXPORT utility, the BMP is corrupted. >> You're correct, it's the TBlobField handling - it's inserting a Paradox graphic header in the bitmaps when assigning a TGraphic field a bitmap. I'll make sure this is fixed in the next build. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, April 24, 2024 at 11:07 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |