Pardon the newbie question.

I want to do some importing and exporting of data thats in an internal
record structure.  The Scalabium SMImport and SMExport look like they'll
handle the job on the one side.

Am I better of to use a TClientDataSet or can I just use a EDBTable?   This
app does not use EDB so there isn't an engine or server.

The idea is that by propograting the date into a dataset, then I can use the
tools available to eliminate the "grunt work" of the different file
formates.

Input welcome.

Lance

Lance,

<< Am I better of to use a TClientDataSet or can I just use a EDBTable?
This app does not use EDB so there isn't an engine or server. >>

How many rows are we talking about ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Unknown.

Most likely anywhere from 100 to 10,000.

Lance



"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:E4AB373F-EE3F-47F6-879B-7BA0DA0B0506@news.elevatesoft.com...
> Lance,
>
> << Am I better of to use a TClientDataSet or can I just use a EDBTable?
> This app does not use EDB so there isn't an engine or server. >>
>
> How many rows are we talking about ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Lance,

<< Most likely anywhere from 100 to 10,000. >>

In that case you could get away with either without problem.  If you start
getting into the 30,000 to 50,000 row range, then using an EDB in-memory
table might be a better option.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Lance R" <lance@cdesoftware.com> wrote in news:BC9DFAE5-8B5F-47F4-B0C8-
5FED760771A9@news.elevatesoft.com:

> propograting

lovely word !

--
Chris
(XP-Pro + Delphi 7 Architect + DBISAM 4.25 build 3 + EDB 1.00 build 6)

Cool.

So to make sure I undestand correctly, I can throw a EDB Table on a form and
use it for the dataset and not need session, engine, etc.

Lance



"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:4C97F8A7-A813-4845-BB66-FE55B5162848@news.elevatesoft.com...
> Lance,
>
> << Most likely anywhere from 100 to 10,000. >>
>
> In that case you could get away with either without problem.  If you start
> getting into the 30,000 to 50,000 row range, then using an EDB in-memory
> table might be a better option.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Lance,

<< So to make sure I undestand correctly, I can throw a EDB Table on a form
and use it for the dataset and not need session, engine, etc. >>

Well, you'll need to at least still set the engine and session properties in
the same way that it is done in the local tutorial here:

http://www.elevatesoft.com/edb1d7_local_application_tutorial.htm

Specifically, the TEDBEngine.ConfigPath, and TEDBSession.LoginUser and
TEDBSession.LoginPassword properties must be set beforehand.   You can use
the global Engine and Session functions in the edbcomps.pas unit instead of
actually creating these components, but you still have to set the properties
to valid values in order to use any part of the ElevateDB engine.

--
Tim Young
Elevate Software
www.elevatesoft.com