Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Stuck in DbSys and can't get out. Send help. :)
Fri, Jun 29 2007 11:39 PMPermanent Link

Dave Harrison
I'm using DbSys for v4.24 and I'm modifying an existing record
structure. Everything was going fine, I added a dozen new fields (using
INS key) tot he old record structure then I went down to the bottom with
the down arrow and entered a new field. As soon as I try and leave the
field name, it says "This field name already exists". Well, this is a
unique field name. I also notice the field # column is the same as the
field above. Shouldn't the field # be incremented?

Now no matter what I do I keep seeing this error dialog pop up. I can't
abort the last field entered. I suppose I could press Cancel and lose
all my changes but I'd rather not do that. But I pressed Cancel anyways
and it tells me "This field name already exists" and sends me back to
the last field entered. I'm stuck in DbSys and can't get out. Smile

I finally pressed Ctrl-D to delete the last field and it gets deleted
and dbSys seems to be ok now. I can add the field just fine if I insert
it with INS, but if I try and add a new field by scrolling down to the
bottom with the arrow key, it screws up.

Is this a known bug?

Dave
Mon, Jul 2 2007 12:49 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Dave,

<< I finally pressed Ctrl-D to delete the last field and it gets deleted and
dbSys seems to be ok now. I can add the field just fine if I insert it with
INS, but if I try and add a new field by scrolling down to the bottom with
the arrow key, it screws up. >>

So, the field name is not a duplicate, but the field # is being duplicated ?
I'd have to know the steps that you took to get this to happen in order to
fix it because I've never seen such a thing happen, at least not in the last
2 years.  There may have been issues like this when V4 first came out.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Jul 3 2007 10:58 AMPermanent Link

Dave Harrison
Tim Young [Elevate Software] wrote:

> Dave,
>
> << I finally pressed Ctrl-D to delete the last field and it gets deleted and
> dbSys seems to be ok now. I can add the field just fine if I insert it with
> INS, but if I try and add a new field by scrolling down to the bottom with
> the arrow key, it screws up. >>
>
> So, the field name is not a duplicate, but the field # is being duplicated ?

Correct, as soon as I press the down arrow to create a new field at the
end of the file list.

> I'd have to know the steps that you took to get this to happen in order to
> fix it because I've never seen such a thing happen, at least not in the last
> 2 years.  There may have been issues like this when V4 first came out.

I'm using 4.25. I tried it again this morning and it is working fine.
When I press the down arrow to create a new field at the end of the
field list, the field # column is now set to 0 which is correct. Before
it would be 39 which was the same field# as the last field in the table.
Maybe there was a memory problem with my machine? I was able to
reproduce the problem countless number of times before, but I guess I
should have rebooted before posting. Oh well. Sorry for the false alarm.

Dave
Tue, Jul 3 2007 3:07 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Dave,

<< I'm using 4.25. I tried it again this morning and it is working fine.
When I press the down arrow to create a new field at the end of the field
list, the field # column is now set to 0 which is correct. Before it would
be 39 which was the same field# as the last field in the table. Maybe there
was a memory problem with my machine? I was able to
reproduce the problem countless number of times before, but I guess I should
have rebooted before posting. Oh well. Sorry for the false alarm. >>

I suspect that it was just a very unique set of circumstances that I never
anticipated, and it screwed up the field # assignment.   It is/was most
definitely a bug, but I'm unfortunately not able to do anything without
being able to reproduce it.  I will try some things here and see if I can
come up with the same result.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Jul 3 2007 4:25 PMPermanent Link

Dave Harrison
Tim Young [Elevate Software] wrote:

> Dave,
>
> << I'm using 4.25. I tried it again this morning and it is working fine.
> When I press the down arrow to create a new field at the end of the field
> list, the field # column is now set to 0 which is correct. Before it would
> be 39 which was the same field# as the last field in the table. Maybe there
> was a memory problem with my machine? I was able to
> reproduce the problem countless number of times before, but I guess I should
> have rebooted before posting. Oh well. Sorry for the false alarm. >>
>
> I suspect that it was just a very unique set of circumstances that I never
> anticipated, and it screwed up the field # assignment.   It is/was most
> definitely a bug, but I'm unfortunately not able to do anything without
> being able to reproduce it.  I will try some things here and see if I can
> come up with the same result.
>

As Arnie would say, "No problem-o". Smile
If it happens again, I'll just reboot since that seemed to have solved
the problem because it's working today.

Dave
Tue, Jul 3 2007 7:05 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Dave,

<< As Arnie would say, "No problem-o". SmileIf it happens again, I'll just
reboot since that seemed to have solved
the problem because it's working today. >>

I actually didn't really read the title of your post yesterday since I
usually speed-reply on Mondays, but I just caught it - it made my day. Smiley

--
Tim Young
Elevate Software
www.elevatesoft.com

Image