> No installation to hard drive and I cannot set up ODBC DNS for the
database.

> Any pointers on which would be best?
> I was going to think about using the TDatabase etc.. but they would
require
> BDE [right?] and hence an install would be needed.

> Thanks

> [I know if I get desperate, I can create a series of flat files and parse
on
> my own... but a db may be a bit easier in the long run]

> No installation to hard drive and I cannot set up ODBC DNS for the
database.

> Any pointers on which would be best?

>No installation to hard drive and I cannot set up ODBC DNS for the database.

>Any pointers on which would be best?
>I was going to think about using the TDatabase etc.. but they would require
>BDE [right?] and hence an install would be needed.

> >No installation to hard drive and I cannot set up ODBC DNS for the
database.

> >Any pointers on which would be best?
> >I was going to think about using the TDatabase etc.. but they would
require
> >BDE [right?] and hence an install would be needed.

> No Tdataset does not require BDE.  TBDEDataset is a Tdataset descendant
that
> requires BDE.  Ttable and Tquery descend from TBDEDataset.

> If you have to run only off the CD does this mean that all files are on
the CD
> and ReadOnly?
> If the files you need to read data from are on the CD and they are not
large I
> would probably use TclientDataset and just use its LoadfromFile SavetoFile
> methods.  This can use either a binary file format or XML.

> You can use ADO and create the connectionstring at runtime.  Nothing needs
to be
> saved on the PC but the PC will have to have ADO installed on it.

> If you look at 3rd party database drivers DbIsam is probably the best
suited for
> a contained distribution like this.  Its drivers compile into the .exe and
are
> quite small.

> --
> Brian Bushay (TeamB)
> Bbus...@NMPLS.com

> >No installation to hard drive and I cannot set up ODBC DNS for the
database.

> >Any pointers on which would be best?
> >I was going to think about using the TDatabase etc.. but they would
require
> >BDE [right?] and hence an install would be needed.

> No Tdataset does not require BDE.  TBDEDataset is a Tdataset descendant
that
> requires BDE.  Ttable and Tquery descend from TBDEDataset.

> If you have to run only off the CD does this mean that all files are on
the CD
> and ReadOnly?
> If the files you need to read data from are on the CD and they are not
large I
> would probably use TclientDataset and just use its LoadfromFile SavetoFile
> methods.  This can use either a binary file format or XML.

> You can use ADO and create the connectionstring at runtime.  Nothing needs
to be
> saved on the PC but the PC will have to have ADO installed on it.

> If you look at 3rd party database drivers DbIsam is probably the best
suited for
> a contained distribution like this.  Its drivers compile into the .exe and
are
> quite small.

> --
> Brian Bushay (TeamB)
> Bbus...@NMPLS.com

> [The HTTP://www.borland.com/midas page no longer exists. [The page
referred
> to
> in the DEPLOY.TXT file.]

> I am using Delphi 5 enterprise, btw.

> Steve
> * @ daves desk

> "Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
> news:od84gu8hr8regckvelmtk4vcqqsel42nog@4ax.com...
> > >I have a customer who is requesting that I create a database and front
> end
> > >[of my choice, so likely delphi] that runs SOLELY from the CD.

> > >No installation to hard drive and I cannot set up ODBC DNS for the
> database.

> > >Any pointers on which would be best?
> > >I was going to think about using the TDatabase etc.. but they would
> require
> > >BDE [right?] and hence an install would be needed.

> > No Tdataset does not require BDE.  TBDEDataset is a Tdataset descendant
> that
> > requires BDE.  Ttable and Tquery descend from TBDEDataset.

> > If you have to run only off the CD does this mean that all files are on
> the CD
> > and ReadOnly?
> > If the files you need to read data from are on the CD and they are not
> large I
> > would probably use TclientDataset and just use its LoadfromFile
SavetoFile
> > methods.  This can use either a binary file format or XML.

> > You can use ADO and create the connectionstring at runtime.  Nothing
needs
> to be
> > saved on the PC but the PC will have to have ADO installed on it.

> > If you look at 3rd party database drivers DbIsam is probably the best
> suited for
> > a contained distribution like this.  Its drivers compile into the .exe
and
> are
> > quite small.

> > --
> > Brian Bushay (TeamB)
> > Bbus...@NMPLS.com

> --Quote START--
> Follow the Data Packet The way you use the MIDAS data packet determines
> whether you need to purchase a MIDAS deployment license or not.
> To me, this is the simplest way to put the licensing requirements:
>     If the MIDAS data packet goes from one machine to another by any
means,
> a license is required
>     If the MIDAS data packet always stays on the same machine, you do not
> need a license.

> "By any means" includes copying to a floppy, using email, copying from one
> hard drive to another, backing up from one machine and restoring on
another
> then resolving the data, and so on. Basically, any method of transferring
> the data packet from one machine to another.

> --Quote END--

> I'll be distributing data but not data packets.  The 'By any means' scares
> me a bit.
> If I use the saveasfile, I think that would be distributing their data
> packet [right?].

> I could use an xml file and use my own routines to bring it into a dataset
> and not
> have to worry about the clientdataset, but am not sure about populating a
> non-connected dataset.  I'll have to look into that.

> Steve@Dave's.Desk

> "David Gley" <dg...@anteon.com> wrote in message news:3d04bd9d_1@dnews...
> > There may be as many 30 recipients of the CD.  Wouldn't the
ClientDataSet
> > require a MIDAS license for each?
> > The Deploy.TXT, Delphi Help and LICENSE.TXT infer that there are
licenses
> > required for each, although it does mention for sharing amongst
computers.
> > Since
> > these would be non cross server apps, does that apply?

> > [The HTTP://www.borland.com/midas page no longer exists. [The page
> referred
> > to
> > in the DEPLOY.TXT file.]

> > I am using Delphi 5 enterprise, btw.

> > Steve
> > * @ daves desk

> > "Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
> > news:od84gu8hr8regckvelmtk4vcqqsel42nog@4ax.com...
> > > >I have a customer who is requesting that I create a database and
front
> > end
> > > >[of my choice, so likely delphi] that runs SOLELY from the CD.

> > > >No installation to hard drive and I cannot set up ODBC DNS for the
> > database.

> > > >Any pointers on which would be best?
> > > >I was going to think about using the TDatabase etc.. but they would
> > require
> > > >BDE [right?] and hence an install would be needed.

> > > No Tdataset does not require BDE.  TBDEDataset is a Tdataset
descendant
> > that
> > > requires BDE.  Ttable and Tquery descend from TBDEDataset.

> > > If you have to run only off the CD does this mean that all files are
on
> > the CD
> > > and ReadOnly?
> > > If the files you need to read data from are on the CD and they are not
> > large I
> > > would probably use TclientDataset and just use its LoadfromFile
> SavetoFile
> > > methods.  This can use either a binary file format or XML.

> > > You can use ADO and create the connectionstring at runtime.  Nothing
> needs
> > to be
> > > saved on the PC but the PC will have to have ADO installed on it.

> > > If you look at 3rd party database drivers DbIsam is probably the best
> > suited for
> > > a contained distribution like this.  Its drivers compile into the .exe
> and
> > are
> > > quite small.

> > > --
> > > Brian Bushay (TeamB)
> > > Bbus...@NMPLS.com

> > http://community.borland.com/article/0,1410,20870,00.html

> Standalone (no deployment license, no BDE)
> For deployment needs where the BDE is either too large or requires too
much
> configuration, MIDAS' TClientDataSet can be used to provide a powerful
> alternative solution. The TClientDataSet component can be used for local
> data storage. You can use the ClientDataSet component to create an
in-memory
> table. Because this table is in-memory, manipulations of it are extremely
> fast. In addition, since it descends from the virtual TDataset class, you
> can use the standard data-aware controls as you always have. If you want
to
> persist the table, you can use the built-in methods SaveToFile and
> LoadFromFile. Also, simply assigning the ClientDataSet.FileName property
> will persist the table automatically.

> This describes exactly my application [the image shown looks much like an
> image I created for the customer during proposals even].  The only
possible
> issue is that
> the database is being replicated and distributed with the application.

> Is there a better area for me to look for licensing issues?

> "David Gley" <dg...@anteon.com> wrote in message

> > --Quote START--
> > Follow the Data Packet The way you use the MIDAS data packet determines
> > whether you need to purchase a MIDAS deployment license or not.
> > To me, this is the simplest way to put the licensing requirements:
> >     If the MIDAS data packet goes from one machine to another by any
> means,
> > a license is required
> >     If the MIDAS data packet always stays on the same machine, you do
not
> > need a license.

> > "By any means" includes copying to a floppy, using email, copying from
one
> > hard drive to another, backing up from one machine and restoring on
> another
> > then resolving the data, and so on. Basically, any method of
transferring
> > the data packet from one machine to another.

> > --Quote END--

> > I'll be distributing data but not data packets.  The 'By any means'
scares
> > me a bit.
> > If I use the saveasfile, I think that would be distributing their data
> > packet [right?].

> > I could use an xml file and use my own routines to bring it into a
dataset
> > and not
> > have to worry about the clientdataset, but am not sure about populating
a
> > non-connected dataset.  I'll have to look into that.

> > Steve@Dave's.Desk

> > "David Gley" <dg...@anteon.com> wrote in message

> > > [The HTTP://www.borland.com/midas page no longer exists. [The page
> > referred
> > > to
> > > in the DEPLOY.TXT file.]

> > > I am using Delphi 5 enterprise, btw.

> > > Steve
> > > * @ daves desk

> > > "Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
> > > news:od84gu8hr8regckvelmtk4vcqqsel42nog@4ax.com...
> > > > >I have a customer who is requesting that I create a database and
> front
> > > end
> > > > >[of my choice, so likely delphi] that runs SOLELY from the CD.

> > > > >No installation to hard drive and I cannot set up ODBC DNS for the
> > > database.

> > > > >Any pointers on which would be best?
> > > > >I was going to think about using the TDatabase etc.. but they would
> > > require
> > > > >BDE [right?] and hence an install would be needed.

> > > > No Tdataset does not require BDE.  TBDEDataset is a Tdataset
> descendant
> > > that
> > > > requires BDE.  Ttable and Tquery descend from TBDEDataset.

> > > > If you have to run only off the CD does this mean that all files are
> on
> > > the CD
> > > > and ReadOnly?
> > > > If the files you need to read data from are on the CD and they are
not
> > > large I
> > > > would probably use TclientDataset and just use its LoadfromFile
> > SavetoFile
> > > > methods.  This can use either a binary file format or XML.

> > > > You can use ADO and create the connectionstring at runtime.  Nothing
> > needs
> > > to be
> > > > saved on the PC but the PC will have to have ADO installed on it.

> > > > If you look at 3rd party database drivers DbIsam is probably the
best
> > > suited for
> > > > a contained distribution like this.  Its drivers compile into the
.exe
> > and
> > > are
> > > > quite small.

> > > > --
> > > > Brian Bushay (TeamB)
> > > > Bbus...@NMPLS.com

> The application you are creating does not access a dataserver to initially
> aquire the dataset nor does it RETURN data to the server.

> Hense,

> From Deploy.txt -- Delphi 6 Enterprise -- (i know you're using D5)
> <snip>

> A server deployment license is not required for deploying
> MIDAS.DLL and STDVCL40.DLL in an application in which
> the client and server reside on the same machine. These two
> files are the Client Dataset Redistributables referred to
> in the License Statement.

> <snip>
> Look for deploy.txt in your root delphi directory.

> I'd still use the TClientDataSet. -- You can create all your tables within
1
> file using the nested dataset capability.

> Doug

> "David Gley" <dg...@anteon.com> wrote in message news:3d04c2dc_1@dnews...
> > From the same page:

> > > http://community.borland.com/article/0,1410,20870,00.html

> > Standalone (no deployment license, no BDE)
> > For deployment needs where the BDE is either too large or requires too
> much
> > configuration, MIDAS' TClientDataSet can be used to provide a powerful
> > alternative solution. The TClientDataSet component can be used for local
> > data storage. You can use the ClientDataSet component to create an
> in-memory
> > table. Because this table is in-memory, manipulations of it are
extremely
> > fast. In addition, since it descends from the virtual TDataset class,
you
> > can use the standard data-aware controls as you always have. If you want
> to
> > persist the table, you can use the built-in methods SaveToFile and
> > LoadFromFile. Also, simply assigning the ClientDataSet.FileName property
> > will persist the table automatically.

> > This describes exactly my application [the image shown looks much like
an
> > image I created for the customer during proposals even].  The only
> possible
> > issue is that
> > the database is being replicated and distributed with the application.

> > Is there a better area for me to look for licensing issues?

> > "David Gley" <dg...@anteon.com> wrote in message
> news:3d04c1a0$1_1@dnews...
> > > http://community.borland.com/article/0,1410,20870,00.html

> > > --Quote START--
> > > Follow the Data Packet The way you use the MIDAS data packet
determines
> > > whether you need to purchase a MIDAS deployment license or not.
> > > To me, this is the simplest way to put the licensing requirements:
> > >     If the MIDAS data packet goes from one machine to another by any
> > means,
> > > a license is required
> > >     If the MIDAS data packet always stays on the same machine, you do
> not
> > > need a license.

> > > "By any means" includes copying to a floppy, using email, copying from
> one
> > > hard drive to another, backing up from one machine and restoring on
> > another
> > > then resolving the data, and so on. Basically, any method of
> transferring
> > > the data packet from one machine to another.

> > > --Quote END--

> > > I'll be distributing data but not data packets.  The 'By any means'
> scares
> > > me a bit.
> > > If I use the saveasfile, I think that would be distributing their data
> > > packet [right?].

> > > I could use an xml file and use my own routines to bring it into a
> dataset
> > > and not
> > > have to worry about the clientdataset, but am not sure about
populating
> a
> > > non-connected dataset.  I'll have to look into that.

> > > Steve@Dave's.Desk

> > > "David Gley" <dg...@anteon.com> wrote in message
> news:3d04bd9d_1@dnews...
> > > > There may be as many 30 recipients of the CD.  Wouldn't the
> > ClientDataSet
> > > > require a MIDAS license for each?
> > > > The Deploy.TXT, Delphi Help and LICENSE.TXT infer that there are
> > licenses
> > > > required for each, although it does mention for sharing amongst
> > computers.
> > > > Since
> > > > these would be non cross server apps, does that apply?

> > > > [The HTTP://www.borland.com/midas page no longer exists. [The page
> > > referred
> > > > to
> > > > in the DEPLOY.TXT file.]

> > > > I am using Delphi 5 enterprise, btw.

> > > > Steve
> > > > * @ daves desk

> > > > "Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
> > > > news:od84gu8hr8regckvelmtk4vcqqsel42nog@4ax.com...
> > > > > >I have a customer who is requesting that I create a database and
> > front
> > > > end
> > > > > >[of my choice, so likely delphi] that runs SOLELY from the CD.

> > > > > >No installation to hard drive and I cannot set up ODBC DNS for
the
> > > > database.

> > > > > >Any pointers on which would be best?
> > > > > >I was going to think about using the TDatabase etc.. but they
would
> > > > require
> > > > > >BDE [right?] and hence an install would be needed.

> > > > > No Tdataset does not require BDE.  TBDEDataset is a Tdataset
> > descendant
> > > > that
> > > > > requires BDE.  Ttable and Tquery descend from TBDEDataset.

> > > > > If you have to run only off the CD does this mean that all files
are
> > on
> > > > the CD
> > > > > and ReadOnly?
> > > > > If the files you need to read data from are on the CD and they are
> not
> > > > large I
> > > > > would probably use TclientDataset and just use its LoadfromFile
> > > SavetoFile
> > > > > methods.  This can use either a binary file format or XML.

> > > > > You can use ADO and create the connectionstring at runtime.
Nothing
> > > needs
> > > > to be
> > > > > saved on the PC but the PC will have to have ADO installed on it.

> > > > > If you look at 3rd party database drivers DbIsam is probably the
> best
> > > > suited for
> > > > > a contained distribution like this.  Its drivers compile into the
> .exe
> > > and
> > > > are
> > > > > quite small.

> > > > > --
> > > > > Brian Bushay (TeamB)
> > > > > Bbus...@NMPLS.com

> The db is rather simple, so not a lot of tables if in a dbm [maybe 7, not
> including list lookups].  Putting as one primary dataset with nested
tables
> within might be
> the most simple method.

> Can I use a dbNavigator to point to a nested dataset?

> [Major dataset is the eoSystems table, a nested dataset may be eoDocuments
> which would be a one to many relationship]

> Steve@Dave's.Desk

> "Douglas Development Group, L. L. C." <infonos...@d-d-g.com> wrote in
> message news:3d04e700_1@dnews...
> > IMHO, you're in the clear.

> > The application you are creating does not access a dataserver to
initially
> > aquire the dataset nor does it RETURN data to the server.

> > Hense,

> > From Deploy.txt -- Delphi 6 Enterprise -- (i know you're using D5)
> > <snip>

> > A server deployment license is not required for deploying
> > MIDAS.DLL and STDVCL40.DLL in an application in which
> > the client and server reside on the same machine. These two
> > files are the Client Dataset Redistributables referred to
> > in the License Statement.

> > <snip>
> > Look for deploy.txt in your root delphi directory.

> > I'd still use the TClientDataSet. -- You can create all your tables
within
> 1
> > file using the nested dataset capability.

> > Doug

> > "David Gley" <dg...@anteon.com> wrote in message

> > > > http://community.borland.com/article/0,1410,20870,00.html

> > > Standalone (no deployment license, no BDE)
> > > For deployment needs where the BDE is either too large or requires too
> > much
> > > configuration, MIDAS' TClientDataSet can be used to provide a powerful
> > > alternative solution. The TClientDataSet component can be used for
local
> > > data storage. You can use the ClientDataSet component to create an
> > in-memory
> > > table. Because this table is in-memory, manipulations of it are
> extremely
> > > fast. In addition, since it descends from the virtual TDataset class,
> you
> > > can use the standard data-aware controls as you always have. If you
want
> > to
> > > persist the table, you can use the built-in methods SaveToFile and
> > > LoadFromFile. Also, simply assigning the ClientDataSet.FileName
property
> > > will persist the table automatically.

> > > This describes exactly my application [the image shown looks much like
> an
> > > image I created for the customer during proposals even].  The only
> > possible
> > > issue is that
> > > the database is being replicated and distributed with the application.

> > > Is there a better area for me to look for licensing issues?

> > > "David Gley" <dg...@anteon.com> wrote in message
> > news:3d04c1a0$1_1@dnews...
> > > > http://community.borland.com/article/0,1410,20870,00.html

> > > > --Quote START--
> > > > Follow the Data Packet The way you use the MIDAS data packet
> determines
> > > > whether you need to purchase a MIDAS deployment license or not.
> > > > To me, this is the simplest way to put the licensing requirements:
> > > >     If the MIDAS data packet goes from one machine to another by any
> > > means,
> > > > a license is required
> > > >     If the MIDAS data packet always stays on the same machine, you
do
> > not
> > > > need a license.

> > > > "By any means" includes copying to a floppy, using email, copying
from
> > one
> > > > hard drive to another, backing up from one machine and restoring on
> > > another
> > > > then resolving the data, and so on. Basically, any method of
> > transferring
> > > > the data packet from one machine to another.

> > > > --Quote END--

> > > > I'll be distributing data but not data packets.  The 'By any means'
> > scares
> > > > me a bit.
> > > > If I use the saveasfile, I think that would be distributing their
data
> > > > packet [right?].

> > > > I could use an xml file and use my own routines to bring it into a
> > dataset
> > > > and not
> > > > have to worry about the clientdataset, but am not sure about
> populating
> > a
> > > > non-connected dataset.  I'll have to look into that.

> > > > Steve@Dave's.Desk

> > > > "David Gley" <dg...@anteon.com> wrote in message
> > news:3d04bd9d_1@dnews...
> > > > > There may be as many 30 recipients of the CD.  Wouldn't the
> > > ClientDataSet
> > > > > require a MIDAS license for each?
> > > > > The Deploy.TXT, Delphi Help and LICENSE.TXT infer that there are
> > > licenses
> > > > > required for each, although it does mention for sharing amongst
> > > computers.
> > > > > Since
> > > > > these would be non cross server apps, does that apply?

> > > > > [The HTTP://www.borland.com/midas page no longer exists. [The page
> > > > referred
> > > > > to
> > > > > in the DEPLOY.TXT file.]

> > > > > I am using Delphi 5 enterprise, btw.

> > > > > Steve
> > > > > * @ daves desk

> > > > > "Brian Bushay TeamB" <BBus...@Nmpls.com> wrote in message
> > > > > news:od84gu8hr8regckvelmtk4vcqqsel42nog@4ax.com...
> > > > > > >I have a customer who is requesting that I create a database
and
> > > front
> > > > > end
> > > > > > >[of my choice, so likely delphi] that runs SOLELY from the CD.

> > > > > > >No installation to hard drive and I cannot set up ODBC DNS for
> the
> > > > > database.

> > > > > > >Any pointers on which would be best?
> > > > > > >I was going to think about using the TDatabase etc.. but they
> would
> > > > > require
> > > > > > >BDE [right?] and hence an install would be needed.

> > > > > > No Tdataset does not require BDE.  TBDEDataset is a Tdataset
> > > descendant
> > > > > that
> > > > > > requires BDE.  Ttable and Tquery descend from TBDEDataset.

> > > > > > If you have to run only off the CD does this mean that all files
> are
> > > on
> > > > > the CD
> > > > > > and ReadOnly?
> > > > > > If the files you need to read data from are on the CD and they
are
> > not
> > > > > large I
> > > > > > would probably use TclientDataset and just use its LoadfromFile
> > > > SavetoFile
> > > > > > methods.  This can use either a binary file format or XML.

> > > > > > You can use ADO and create the connectionstring at runtime.
> Nothing
> > > > needs
> > > > > to be
> > > > > > saved on the PC but the PC will have to have ADO installed on
it.

> > > > > > If you look at 3rd party database drivers DbIsam is probably the
> > best
> > > > > suited for
> > > > > > a contained distribution like this.  Its drivers compile into
the
> > .exe
> > > > and
> > > > > are
> > > > > > quite small.

> > > > > > --
> > > > > > Brian Bushay (TeamB)
> > > > > > Bbus...@NMPLS.com