Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Error 7200

3 posts in FoxPro Last posting was on 2009-11-17 20:27:38.0Z
Eric Selje Posted on 2009-11-17 17:20:57.0Z
From: "Eric Selje" <eselje@tcgcorp.net>
Newsgroups: Advantage.FoxPro
Subject: Error 7200
Date: Tue, 17 Nov 2009 11:20:57 -0600
Lines: 20
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1983
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1983
NNTP-Posting-Host: 206.197.100.68
Message-ID: <4b02db17@solutions.advantagedatabase.com>
X-Trace: 17 Nov 2009 10:19:19 -0700, 206.197.100.68
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!206.197.100.68
Xref: solutions.advantagedatabase.com Advantage.FoxPro:315
Article PK: 1109669

Hi,

I'm doing some testing and having a table locking problem. If I open a
table in VFP, and then try to access that table via a cursorAdaptor in VFP,
I'm getting error 7200. If I explicitly close the shared table in VFP, then
I can open it via the cursorAdaptor.

Other various settings:
SET EXCL is, of course, OFF.
Table types are set to VFP on the Monroe.add, locking is set to "Compatible"
Connection string is:
[driver=Advantage StreamlineSQL ODBC;
DataDirectory=\\madhpquad1\quad1_g\eisdata\mon\MONROE.ADD; TableType=VFP;
UID=AdsSys;Pwd=xxxxxx;]

Thanks!

Eric


Alex Wong (ADS) Posted on 2009-11-17 20:13:39.0Z
From: "Alex Wong \(ADS\)" <nobody@sybase.com>
Newsgroups: Advantage.FoxPro
References: <4b02db17@solutions.advantagedatabase.com>
Subject: Re: Error 7200
Date: Tue, 17 Nov 2009 13:13:39 -0700
Lines: 38
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5843
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: 10.24.38.144
Message-ID: <4b030391@solutions.advantagedatabase.com>
X-Trace: 17 Nov 2009 13:12:01 -0700, 10.24.38.144
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.144
Xref: solutions.advantagedatabase.com Advantage.FoxPro:316
Article PK: 1109670

What is the detailed error text?

I suspect that the problem is the locking mode. Add the following to the
connection string. It may fix the problem:

ADVANTAGELOCKING=OFF

--
Alex

"Eric Selje" <eselje@tcgcorp.net> wrote in message
news:4b02db17@solutions.advantagedatabase.com...
> Hi,
>
> I'm doing some testing and having a table locking problem. If I open a
> table in VFP, and then try to access that table via a cursorAdaptor in
> VFP,
> I'm getting error 7200. If I explicitly close the shared table in VFP,
> then
> I can open it via the cursorAdaptor.
>
> Other various settings:
> SET EXCL is, of course, OFF.
> Table types are set to VFP on the Monroe.add, locking is set to
> "Compatible"
> Connection string is:
> [driver=Advantage StreamlineSQL ODBC;
> DataDirectory=\\madhpquad1\quad1_g\eisdata\mon\MONROE.ADD; TableType=VFP;
> UID=AdsSys;Pwd=xxxxxx;]
>
> Thanks!
>
> Eric
>
>


Eric Selje Posted on 2009-11-17 20:27:38.0Z
From: "Eric Selje" <eselje@tcgcorp.net>
Newsgroups: Advantage.FoxPro
References: <4b02db17@solutions.advantagedatabase.com> <4b030391@solutions.advantagedatabase.com>
Subject: Re: Error 7200
Date: Tue, 17 Nov 2009 14:27:38 -0600
Lines: 5
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1983
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1983
NNTP-Posting-Host: 206.197.100.68
Message-ID: <4b0306d9@solutions.advantagedatabase.com>
X-Trace: 17 Nov 2009 13:26:01 -0700, 206.197.100.68
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!206.197.100.68
Xref: solutions.advantagedatabase.com Advantage.FoxPro:317
Article PK: 1109673

Hey, that worked Alex. Thanks!

On to the next issue (see new thread...)