Hi Guys,
Windows 10, Delphi 10.1, latest DBISAM.
I am converting an old DBF file to DBISAM.  It has several Memo fields.  The conversion processes OK but when I open up the DBISAM table with the System Utility and go to look at the MEMO fields, it tells me the memos have various bytes in them under Memo Size, but they don't show in Memo Contents.  i.e. No text visible.

No doubt I have missed something.

Thoughts/suggestions appreciated.

Regards & TIA,
Ian

Ian


What happens if you write a small test app to get the data, stuff it into a string variable and look at it in the debugger?

Things that go through my mind are some sort of ansi vs unicode clash, non-displaying characters in the memo fields, the memo fields having nulls (#0) in them

Roy Lambert

Hi Roy,
Yes, a clash of Unicode v ANSI was what occurred to me also.
I'll give your debug suggestion a whirl and see what I see.
Cheers.
Ian

Ian,

<< I am converting an old DBF file to DBISAM. >>

How did you perform the conversion ?

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,
Point of clarification, I am converting Apollo DBF/CDX/FPT files.
I used an app from 2003 days.  I recompiled it with D10.1.  It uses SMImport coupled with Apollo & DBISAM.
I found and tried the 2003 version (don't know why I still had an .exe copy) and it worked fine.
Leads me to believe it is Unicode related att.
Whilst my immediate need is resolved, I want to get it going in D10.1.
Regards,
Ian

Ian,

<< Point of clarification, I am converting Apollo DBF/CDX/FPT files. I used an app from 2003 days.  I recompiled it with D10.1.  It uses SMImport coupled with Apollo & DBISAM. I found and tried the 2003 version (don't know why I still had an .exe copy) and it worked fine. Leads me to believe it is Unicode related att. Whilst my immediate need is resolved, I want to get it going in D10.1. >>

Yeah, you might have issues with using older pre-Unicode code with a Delphi Unicode compiler, and might need to use an older version of Delphi for writing the conversion code if you want to avoid having to go through and fix someone else's product to be Unicode-compatible.

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,
To take Delphi/Unicode out of the equation I installed D2007 and all the necessary related components into a VM.
Recompiled the app, again, no changes since the original 2003 code, and get the same result.  Sigh.
Regards,
Ian

Ian


I'm slightly confused now. You're using Apollo, DBISAM and SMImport. I assume you don't have Apollo table components and are using SMImport to pull in the data. If I'm right you need to be looking at what SMImport is producing. If that's the problem and you can't solve it contact Mike Skolnik - he's very helpful.

If I'm wrong just what are you doing?

Roy Lambert

Hi Roy, Tim,
SMImport still requires the Apollo components to read the .dbf file(s).

Found the issue.
It would seem that the .fpt file was corrupt in some manner.  I tried the app on an older file and it worked OK so I ran DBFRecovery over the file I was trying to convert and Bingo! all good now.  Most strange as there were no issues reading the .fpt Memos in Apollo.
Thank you both for your responses to my issue.
Regards,
Ian

Ian


>SMImport still requires the Apollo components to read the .dbf file(s).

How very strange. Must be something specific to Apollo since I can use SMImport to read DBFs without anything else installed.

Roy