I agree. I use C++ Builder Pro and Ent. and Delphi Pro and we use editable
grids when ever we can, the customer's can quickly make all the necessary
changes they want and it's easier to develop. But I roll my own
connectivity components for the varies databases that we deal with, so we
NEVER have a problem because a user went to lunch in the middle of editing a
record. The only problem they may be faced with is when they finally decide
to commit their changes they get an error saying that "Those records were
modified by another user", and would have to re-enter the changes based off
of fresh data.

So I guess it all comes down to the connectivity components that you are
using, since I roll my own I can't comment on which one's are best.

Thanks

-----Original Message-----
From: Louis Kleiman [mailto:lkleiman@...]
Sent: Wednesday, May 08, 2002 11:39 AM
To: ib-support@yahoogroups.com
Subject: Re: [ib-support] minimizing transaction-open time


Gee. All of my apps for the past three or four years have used
ClientDataSet-based editing in Delphi 4 - 6 against a large variety of
databases from IB to Oracle to SQL Server to Informix.... CDSs present a
great way to cache changes on the client, keep the length of transactions to
an absolute minimum, improve performance by having a fully functional
dataset on the client when required, manage update conflicts, .... I
wouldn't do editable data any way other than via a CDS. In addition, I do a
lot of editable grids. I guarantee that in most cases I can do data entry
faster in a grid that in a page full of fields. Plus, I can often find the
data I want to edit more easily because I can scroll to it and edit it in
place.

Don't get me wrong. I know there are many different ways to skin this cat.
There are also many personal perferences that each of us has. However, I
want many of the newcomers to realize that you don't have to make grids read
only and you don't have to use IB transaction-based locking to build
successful apps.

Louis Kleiman
SSTMS, Inc.

P.S. No, I don't use TTable. No I don't let a user fetch thousands of rows
when he or she should just read one or a few. Yes I do use "select *"
sometimes.

----- Original Message -----
From: Woody
To: ib-support@yahoogroups.com
Sent: Wednesday, May 08, 2002 11:07 AM
Subject: Re: [ib-support] minimizing transaction-open time


From: "Doug Chamberlin" <DChamberlin@...>
> At 05/08/2002 10:37 AM (Wednesday), Woody wrote:
> >Moving between
> >records then becomes: start transaction, read record, edit (or not),
stop
> >transaction, start transaction, read record, etc., etc.
>
> Actually a much better way is
>
> Start trans
> Read record
> Commit
> Let user edit record taking all the time they want.
> When they save:
> Start trans
> Write updates
> Commit

This implies that you either use clientdataset components or non-data
aware
controls. Both of these are usually not acceptable to beginners because of
their fallacies. Also, because I am stuck in a Delphi 5 infinite loop, I
don't have clientdatasets. Writing code to transfer information to and
from
non-data aware controls can be very time consuming and difficult for those
just starting out. That's why I suggest my way instead. You are right,
though, if time and resources permit. <g>


Woody (TMW)


Yahoo! Groups Sponsor
ADVERTISEMENT




To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


[Non-text portions of this message have been removed]



To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/