Headache about "Cannot access the selected table"!!!

Normally, if an error is appeared, my error-handling procedure will be triggered and the
error message will be shown (use WAIT command to achieve) at the right top corner of the
screen. Also the error will be captured to a text file and then I can trace back the
problem.

But I encounter this error which is shown in FoxPro dialog box, and I cannot trace what
the error is in debugging window. I don't know how to solve it. I fully feel that it is
FoxPro's internal error.

How can I do to eliminate this error?

Leonid
Thu Aug 07 08:15:02 CDT 2003

If you have a form with two comboboxes with RowSourceType=3D3 and =
RowSource something like

Select ... into cursor MYCURSOR

both with the same cursor names, you will have this error

Leonid


"Christopher Panadol" <thfchristopher@i-cable.com> wrote in message =
news:OhFR#XNXDHA.416@tk2msftngp13.phx.gbl...
> Normally, if an error is appeared, my error-handling procedure will be =
triggered and the
> error message will be shown (use WAIT command to achieve) at the right =
top corner of the
> screen. Also the error will be captured to a text file and then I can =
trace back the
> problem.
>=20
> But I encounter this error which is shown in FoxPro dialog box, and I =
cannot trace what
> the error is in debugging window. I don't know how to solve it. I =
fully feel that it is
> FoxPro's internal error.
>=20
> How can I do to eliminate this error?
>=20
>=20

Leemi
Thu Aug 07 09:30:07 CDT 2003

Hi Christopher:

I agree with Rick's assessment. This is probably a network problem.

To help track this problem down, you might want to use FileMon available
from www.sysinternals.com . This might provide you with some more
information on what is causing the problem

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retires June 30th, 2003
- VFP6 Mainstream Support retires Sept. 30th, 2003

>Christopher,
>I found that this error is usually due to hardware or network problems -
you've lost the >connection between the local system and the file server.
Check with your network administrator >to track down the real problem
(NICs, cabling, Hub, Router, Switch, etc.) - you won't be able to >do
anything programmatically.
>Rick
>"Christopher Panadol" <thfchristopher@i-cable.com> wrote in message
>news:OhFR%23XNXDHA.416@tk2msftngp13.phx.gbl...
> Normally, if an error is appeared, my error-handling procedure will be
triggered and the
> error message will be shown (use WAIT command to achieve) at the right
top corner of the
> screen. Also the error will be captured to a text file and then I can
trace back the
> problem.
>
> But I encounter this error which is shown in FoxPro dialog box, and I
cannot trace what
> the error is in debugging window. I don't know how to solve it. I fully
feel that it is
> FoxPro's internal error.
>
> How can I do to eliminate this error?

Rick
Thu Aug 07 09:53:57 CDT 2003

Lenoid,
That's good to know - I've never run into that one before. Thanks for =
the insight!

Rick

"Leonid" <leonid@grada.lv> wrote in message =
news:%2327YqXOXDHA.1888@TK2MSFTNGP10.phx.gbl...
If you have a form with two comboboxes with RowSourceType=3D3 and =
RowSource something like

Select ... into cursor MYCURSOR

both with the same cursor names, you will have this error

Leonid


"Christopher Panadol" <thfchristopher@i-cable.com> wrote in message =
news:OhFR#XNXDHA.416@tk2msftngp13.phx.gbl...
> Normally, if an error is appeared, my error-handling procedure will be =
triggered and the
> error message will be shown (use WAIT command to achieve) at the right =
top corner of the
> screen. Also the error will be captured to a text file and then I can =
trace back the
> problem.
>=20
> But I encounter this error which is shown in FoxPro dialog box, and I =
cannot trace what
> the error is in debugging window. I don't know how to solve it. I =
fully feel that it is
> FoxPro's internal error.
>=20
> How can I do to eliminate this error?
>=20
>=20

Jack
Thu Aug 07 16:26:21 CDT 2003

In article <OhFR#XNXDHA.416@tk2msftngp13.phx.gbl>, thfchristopher@i-
cable.com says...
> Normally, if an error is appeared, my error-handling procedure will be triggered and the
> error message will be shown (use WAIT command to achieve) at the right top corner of the
> screen. Also the error will be captured to a text file and then I can trace back the
> problem.
>
> But I encounter this error which is shown in FoxPro dialog box, and I cannot trace what
> the error is in debugging window. I don't know how to solve it. I fully feel that it is
> FoxPro's internal error.
>
> How can I do to eliminate this error?

I know of two things that will cause this error:

1. As someone else has posted here, two comboboxes with RowSourceType =
3 and a Select statement with the same cursor name.

2. Destroying a cursor that is the RowSource for a combobox (and maybe
a listbox too). The next time the control refreshes, it will give an
error. We ran into this one because we use a class to open remote
views, and when the form exits if the class that opened the remote view
was destroyed before the control the view cursor would be destroyed when
the control still pointed to the cursor.

EFGroup
Wed Aug 13 11:32:42 CDT 2003

It might be that your table is in some other data session ? rare - but it
happened on me a few times this year with vfp 8 on a form ..
hth - mondo regards [Will]

--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:excel-info@efgroup.net
mySql / VFP / MS-SQL
"Christopher Panadol" <thfchristopher@i-cable.com> wrote in message
news:OhFR#XNXDHA.416@tk2msftngp13.phx.gbl...
> Normally, if an error is appeared, my error-handling procedure will be
triggered and the
> error message will be shown (use WAIT command to achieve) at the right top
corner of the
> screen. Also the error will be captured to a text file and then I can
trace back the
> problem.
>
> But I encounter this error which is shown in FoxPro dialog box, and I
cannot trace what
> the error is in debugging window. I don't know how to solve it. I fully
feel that it is
> FoxPro's internal error.
>
> How can I do to eliminate this error?
>
>