Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 7 of 7 total
Thread D7 with DBISAM 4.29B4 Table.Insert
Tue, Jun 8 2010 4:34 PMPermanent Link

John Postnikoff


It seems with the last update that I have the behavior of CopyOnAppend set to true. When my tell my application to insert a blank record it is bringing data in to the blank record.  I did not change any code after the upgrade. Even if I try to set tabel.CopyOnAppend :=false i get the same results.  Any ideas?

John Postnikoff
Wed, Jun 9 2010 11:10 AMPermanent Link

Robert Kaplan


<John Postnikoff> wrote in message
news:EABBBA89-87E3-4766-9F0E-2AC42A8DFA79@news.elevatesoft.com...
>
> It seems with the last update that I have the behavior of CopyOnAppend set
> to true. When my tell my application to insert a blank record it is
> bringing data in to the blank record.  I did not change any code after the
> upgrade. Even if I try to set tabel.CopyOnAppend :=false i get the same
> results.  Any ideas?
>

Do you see this behavior with dbsys? Open any table and click insert, is the
new record populated?

Robert

Wed, Jun 9 2010 1:43 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

John,

<< It seems with the last update that I have the behavior of CopyOnAppend
set to true. When my tell my application to insert a blank record it is
bringing data in to the blank record.  I did not change any code after the
upgrade. Even if I try to set tabel.CopyOnAppend :=false i get the same
results.  Any ideas? >>

I'm not seeing this behavior here with 4.29 B4.

What version/build were you using prior to installing 4.29 B4 ?

--
Tim Young
Elevate Software
www.elevatesoft.com
Wed, Jun 9 2010 10:57 PMPermanent Link

John Postnikoff

I think I was using 4.29 B3 (not 100% sure on what build).    If I use the utility it seems to work OK.  It seems fine by using the DBSYS utility. However, I did not change my code.  

"Tim Young [Elevate Software]" wrote:

John,

<< It seems with the last update that I have the behavior of CopyOnAppend
set to true. When my tell my application to insert a blank record it is
bringing data in to the blank record.  I did not change any code after the
upgrade. Even if I try to set tabel.CopyOnAppend :=false i get the same
results.  Any ideas? >>

I'm not seeing this behavior here with 4.29 B4.

What version/build were you using prior to installing 4.29 B4 ?

--
Tim Young
Elevate Software
www.elevatesoft.com
Wed, Jun 9 2010 10:58 PMPermanent Link

John Postnikoff

OK with DBSYS.

"Robert K" wrote:


<John Postnikoff> wrote in message
news:EABBBA89-87E3-4766-9F0E-2AC42A8DFA79@news.elevatesoft.com...
>
> It seems with the last update that I have the behavior of CopyOnAppend set
> to true. When my tell my application to insert a blank record it is
> bringing data in to the blank record.  I did not change any code after the
> upgrade. Even if I try to set tabel.CopyOnAppend :=false i get the same
> results.  Any ideas?
>

Do you see this behavior with dbsys? Open any table and click insert, is the
new record populated?

Robert
Thu, Jun 10 2010 1:13 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

John,

<< OK with DBSYS. >>

If it works okay with the same version/build of DBSYS, then you need to
double-check that:

1) You're using the same version/build in your app
2) That you don't have an error in your code

--
Tim Young
Elevate Software
www.elevatesoft.com
Thu, Jun 10 2010 2:01 PMPermanent Link

Robert Kaplan


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:9DC04A14-FF96-45F9-BCEF-8694A29D27AB@news.elevatesoft.com...
> John,
>
> << OK with DBSYS. >>
>
> If it works okay with the same version/build of DBSYS, then you need to
> double-check that:
>
> 1) You're using the same version/build in your app
> 2) That you don't have an error in your code
>
I doubt if any version had such a horrendous bug. There's probably some
OnNewRecord or AfterInsert code, and/or defaults set for the DBISAM table
(though those would have showed up on DBSYS, if the test was done on the
same table).

Robert

Image