Hi,

Any idea for the error message:

"ElevateDB Error #1010 The row is no longer visible in the table xxxxx"

When I try to modify exsiting records, only happen once for one table.

Jianfei

Jianfei,

<< Any idea for the error message:

"ElevateDB Error #1010 The row is no longer visible in the table xxxxx"

When I try to modify exsiting records, only happen once for one table. >>

This is an "expected" error, and is used to indicate to you that the row
that you modified has fallen out of the scope of the current filter and/or
query WHERE clause.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi, Tim

I am using the master and detail link through dataset. The records show
there how can the records out of scope.
After close error message, I can still modify that records without problem.
How can I fix this problem?

Thanks

Jianfei


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:52918EA8-07F9-4AA3-A0FA-609F6B4C948B@news.elevatesoft.com...
> Jianfei,
>
> << Any idea for the error message:
>
> "ElevateDB Error #1010 The row is no longer visible in the table xxxxx"
>
> When I try to modify exsiting records, only happen once for one table. >>
>
> This is an "expected" error, and is used to indicate to you that the row
> that you modified has fallen out of the scope of the current filter and/or
> query WHERE clause.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Hi, Tim

Fisrt Record in Detail is OK to be Modified. If I change master record and
modified the record I will get this error message, however if the record is
the fisrt record, It works OK. Also, if I close the error message box, I can
modify the rest records.

My key Field is GUID field type.

Any idea?

Jianfei


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:52918EA8-07F9-4AA3-A0FA-609F6B4C948B@news.elevatesoft.com...
> Jianfei,
>
> << Any idea for the error message:
>
> "ElevateDB Error #1010 The row is no longer visible in the table xxxxx"
>
> When I try to modify exsiting records, only happen once for one table. >>
>
> This is an "expected" error, and is used to indicate to you that the row
> that you modified has fallen out of the scope of the current filter and/or
> query WHERE clause.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Hi, Tim

I tried to trace the problem. It looks like the CursorRowsetNavigator
somehow not right. After I refresh the TEDBTable (this is detail table) then
try to modify the detail record, I will get this error. The LockedRowNumber
is right, but RowNumber always returns 1.

Any idea how to fix this?

Jianfei


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:52918EA8-07F9-4AA3-A0FA-609F6B4C948B@news.elevatesoft.com...
> Jianfei,
>
> << Any idea for the error message:
>
> "ElevateDB Error #1010 The row is no longer visible in the table xxxxx"
>
> When I try to modify exsiting records, only happen once for one table. >>
>
> This is an "expected" error, and is used to indicate to you that the row
> that you modified has fallen out of the scope of the current filter and/or
> query WHERE clause.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Hi, Tim

It looks like the detail table somehow got master's dataset
FRowsetNavigator. How can that happen and how to fix this?

Jianfei

"Jianfei Xu" <jxu@DRAXware.com> wrote in message
news:76451C95-B15D-400A-B48D-9E193031DC5C@news.elevatesoft.com...
> Hi, Tim
>
> I tried to trace the problem. It looks like the CursorRowsetNavigator
> somehow not right. After I refresh the TEDBTable (this is detail table)
> then try to modify the detail record, I will get this error. The
> LockedRowNumber is right, but RowNumber always returns 1.
>
> Any idea how to fix this?
>
> Jianfei
>
>
> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
> news:52918EA8-07F9-4AA3-A0FA-609F6B4C948B@news.elevatesoft.com...
>> Jianfei,
>>
>> << Any idea for the error message:
>>
>> "ElevateDB Error #1010 The row is no longer visible in the table xxxxx"
>>
>> When I try to modify exsiting records, only happen once for one table. >>
>>
>> This is an "expected" error, and is used to indicate to you that the row
>> that you modified has fallen out of the scope of the current filter
>> and/or query WHERE clause.
>>
>> --
>> Tim Young
>> Elevate Software
>> www.elevatesoft.com
>>
>
>

Jianfei,

<< I am using the master and detail link through dataset. The records show
there how can the records out of scope.
After close error message, I can still modify that records without problem.
How can I fix this problem? >>

Could you send me an example of what you're trying to do ?  I am having a
hard time envisioning what you're doing.

--
Tim Young
Elevate Software
www.elevatesoft.com

Jianfei,

<< Fisrt Record in Detail is OK to be Modified. If I change master record
and modified the record I will get this error message, however if the record
is the fisrt record, It works OK. Also, if I close the error message box, I
can modify the rest records. >>

Are you modifying the key values for any of the detail rows ?  If so, are
you saying that you're also modifying the master row at the same time ?

--
Tim Young
Elevate Software
www.elevatesoft.com

I just want to modify the record (not Key Value);

Right now, I just call UpdateCursorPos when Mouse enter the Grid Editor to
solve the issue.

I did switch to ADO, no problem for SQL Server.

Jianfei


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:D6A21E03-C86E-4CE8-A8C0-B5087D7B6219@news.elevatesoft.com...
> Jianfei,
>
> << Fisrt Record in Detail is OK to be Modified. If I change master record
> and modified the record I will get this error message, however if the
> record is the fisrt record, It works OK. Also, if I close the error
> message box, I can modify the rest records. >>
>
> Are you modifying the key values for any of the detail rows ?  If so, are
> you saying that you're also modifying the master row at the same time ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Tim


I've had this error a couple of times as well. Since I was fighting some other code at the time I've pretty much ignored it just now, but I can say with some level of certainty  that I didn't alter any field that would cause it to move out of scope. In my case (from memory) I was setting a range and then using a timer to set a flag in the current record (think email - read/not read status). The record was still there after the flag had been set as it should be and the error message and its description in the manual had me thinking "oh look the new 8708"

I haven't done anything to track it down as Jianfei has but I can confirm it exists.

1.09b3 just so you know

Roy Lambert