> 273K DLL + your app small enough? :)
Yes, that is just fine, the size is not really the issue, more important to me is to
minimise the overhead/impact on the users system - and the risks of corrupting or
otherwise affecting their system.
On this note, has anyone used the MS Jet Access across a wide number of sites ?
Generally OK, or some problems ?
[ The reason I ask, I got a program from Oz last year, developed in Delphi, and using
the MS Jet Access stuff. On every (Win 95 or 98) system I installed it on, there was
subsequently a "Windows is updating the following programs" msg at boot up (every
time, not just the first time, taking an extra 5-10 seconds - and frustrating), and on
one machine it corrupted the users desktop wallpaper setup. Correcting the wallpaper
setup worked only until the PC was rebooted - until I used RegRun to remove the entry
from the registry, and the problem went away. Similarly with the "Windows is
updating the following programs" msg. And it all happened when I installed the MS
Jet Access stuff associated with that program. ]
The engineering program under development really only needs simple flat file access.
I did a similar complexity program a few years ago using D1, wrote my own simple
readonly flat file database handler, no system hooks etc, program is now on well over
a 1000 PC's around the country - and I've had absolutely no system support problems.
While I accept that the developer finds it easier to develop using Jet Access stuff
... (the joys of VB ...) if we don't need the relational database stuff, why not use
the KISS principle ? Am I being paranoid about this Jet Access stuff - or just
healthily cynical ?
Comments appreciated.
TIA
Geoff
> -----Original Message-----
> From: Nic Wise [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, February 07, 2001 11:36 AM
> To: Multiple recipients of list delphi
> Subject: Re: [DUG]: D3 - ClientDataSet
>
> > ClientDataSet is in both the printed documentation and the online help of
> my (Pro) version - so I assume it should be part of my version.
>
> I thought it would be in pro, but it appears to be only in Enterprise
> ( Check to see if you have a MIDAS tab tho - I could have sworn that MIDAS
> is in Delphi 5 pro.... There are other ones tho - check out
> www.kylecordes.com (I think) for the bde alternatives guide.
>
> >
> > All I want to do is to use the simple flat file local database access/save
> capability (ie NO BDE), which, while it used for the briefcase model of the
> three tier stuff, should also be available for simple apps, single user,
> with minimal database requirements.
> >
>
> you should read this then:
> http://community.borland.com/article/0,1410,20870,00.html
>
> especially this bit:
> 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.
>
>
> > What I'm really wanting to do is to kick butt with a joint venture
> project, where the (VB) programmer is using the powerful & fancy Jet access
> engine stuff (with all its system hooks, risks etc), when simple flat file
> local database would do for the simple read-only data we need. This
> program will be on hundreds of computers around the country, and I want to>
> minimise the footprint and impact on users systems - and the risk of
> help/support calls, as I've had problems with Jet Access before.
>
> 273K DLL + your app small enough? :)
>
>
> > If TClientDataSet is only available in the Enterprise version, does anyone
> have a reccommended simple, easy third party database access component
> they've used and can reccommend ?
> >
>
>
> ---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
> To UnSub, send email to: [EMAIL PROTECTED]
> with body of "unsubscribe delphi"
>
EOM
NOTICE - This message contains information intended only for the use of the addressee
named above. It may also be confidential and/or privileged. If you are not the
intended recipient of this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it. If you have received this
message in error please notify [EMAIL PROTECTED]
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
