I use SMI import tools by Scalabium Software to move import data on a regular basis with many applications. Since upgrading to DBISAM 4.29 and 4.30 it seems that I get errors on the import and the import is much slower with tables that contain memo fields. If I remove the memo field from the table the errors will go away, however speed is still an issue.  It is something to do with the memo fields for sure. I have updated and rebuild all tables if I run my application built with version 4.25 B 7 with the same dataset the errors do not occur.

I will also forward to Mike Shkolnik of Scalabium.

Any help is appreciated.

John

John,

<< I use SMI import tools by Scalabium Software to move import data on a
regular basis with many applications. Since upgrading to DBISAM 4.29 and
4.30 it seems that I get errors on the import and the import is much slower
with tables that contain memo fields. If I remove the memo field from the
table the errors will go away, however speed is still an issue.  It is
something to do with the memo fields for sure. I have updated and rebuild
all tables if I run my application built with version 4.25 B 7 with the same
dataset the errors do not occur. >>

Is this a single-user or multi-user application ?  If multi-user, C/S or
file-sharing ?

--
Tim Young
Elevate Software
www.elevatesoft.com

In this case this is a local - a single user application that is set to import and consolidate data from many workstations. I am using D7 under Windows XP with the CS version set to local. Sorry I will be away for a good week if you need more details. Will not be able to check in earlier.

John


"Tim Young [Elevate Software]" wrote:

John,

<< I use SMI import tools by Scalabium Software to move import data on a
regular basis with many applications. Since upgrading to DBISAM 4.29 and
4.30 it seems that I get errors on the import and the import is much slower
with tables that contain memo fields. If I remove the memo field from the
table the errors will go away, however speed is still an issue.  It is
something to do with the memo fields for sure. I have updated and rebuild
all tables if I run my application built with version 4.25 B 7 with the same
dataset the errors do not occur. >>

Is this a single-user or multi-user application ?  If multi-user, C/S or
file-sharing ?

--
Tim Young
Elevate Software
www.elevatesoft.com

John,

<< In this case this is a local - a single user application that is set to
import and consolidate data from many workstations. I am using D7 under
Windows XP with the CS version set to local. Sorry I will be away for a good
week if you need more details. Will not be able to check in earlier.  >>

Do you have any examples of the error messages that you're seeing with 4.30
?  If anything, 4.28 and higher should be faster than 4.27 and earlier, due
to the BLOB re-design.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

The errors are reported SMImport errors on the import tools with the newer versions and not DBISAM xxxx errors.  They do not have a reference number. It justs says import complete with errors, and in this case the data from the memo fields will not import into the destination table from the source.

John.


"Tim Young [Elevate Software]" wrote:

John,

<< In this case this is a local - a single user application that is set to
import and consolidate data from many workstations. I am using D7 under
Windows XP with the CS version set to local. Sorry I will be away for a good
week if you need more details. Will not be able to check in earlier.  >>

Do you have any examples of the error messages that you're seeing with 4.30
?  If anything, 4.28 and higher should be faster than 4.27 and earlier, due
to the BLOB re-design.

--
Tim Young
Elevate Software
www.elevatesoft.com

John,

<< The errors are reported SMImport errors on the import tools with the
newer versions and not DBISAM xxxx errors.  They do not have a reference
number. It justs says import complete with errors, and in this case the data
from the memo fields will not import into the destination table from the
source. >>

Did Mike from Scalabium get back to you with any more information ?  This
sounds like they need to change around some of their code for 4.28 or
higher, due to the BLOB redesign.  However, if he's using just straight data
access code through a TDBISAMTable component, then the problem may be on our
end.

--
Tim Young
Elevate Software
www.elevatesoft.com

I did not get a reply form Mike. He usually responds in a very short time frame. I will try to get more details on my end as I was out of the country for a while and just getting back to work on this.


"Tim Young [Elevate Software]" wrote:

John,

<< The errors are reported SMImport errors on the import tools with the
newer versions and not DBISAM xxxx errors.  They do not have a reference
number. It justs says import complete with errors, and in this case the data
from the memo fields will not import into the destination table from the
source. >>

Did Mike from Scalabium get back to you with any more information ?  This
sounds like they need to change around some of their code for 4.28 or
higher, due to the BLOB redesign.  However, if he's using just straight data
access code through a TDBISAMTable component, then the problem may be on our
end.

--
Tim Young
Elevate Software
www.elevatesoft.com

I also had some issues with SMExport and DBISam V4. Export worked fine under
DBISam V3 but when i upgraded to DBISam V4 only the first record would be
exported. All other records were ignored.

Like you, I also highlighted to Mike from Scalabium but never got a reply.
Managed to find a workaround though. Instead of connecting the Export
component directly to the dataset (DBISamTable), I connected it to a DBGrid.
So SMExport connected to DBGrid, DBGrid connect to DBISamTable . Its a
little long winded but it did solve my problem. Not sure if it workable on
your import but worth looking into if you don't get a reponse from Mike.


Regards
Gregory Sebastian

I have updated to DBISAM 4.30 B2 and my memo data seems be coming through, however SMI import is still reporting errors and the transfer process is still very slow as compared to before.  So far I cannot see what the data errors are.  I think in this case Mike from Scalabium will have collaborate with Tim. I will offer my data. In the meantime I will try your suggestion to satisfy my customer.

Thanks.

John Postnikoff



"Gregory Sebastian" wrote:

I also had some issues with SMExport and DBISam V4. Export worked fine under
DBISam V3 but when i upgraded to DBISam V4 only the first record would be
exported. All other records were ignored.

Like you, I also highlighted to Mike from Scalabium but never got a reply.
Managed to find a workaround though. Instead of connecting the Export
component directly to the dataset (DBISamTable), I connected it to a DBGrid.
So SMExport connected to DBGrid, DBGrid connect to DBISamTable . Its a
little long winded but it did solve my problem. Not sure if it workable on
your import but worth looking into if you don't get a reponse from Mike.


Regards
Gregory Sebastian