main logo
Subject: Re: SQL 7 upsizing error in PK fields.
Author: Bob Archer
Posted: 2000/10/22 16:59:37
 
View Entire Thread
New Search


You're not really opening tables right, you are opening remote views? Make sure the UPDATE page of the remote view defines the primary key properly.

BOb


<I><FONT COLOR="#663300">I've upsized my VFP 6 CB project to SQL 7 using the wizard w/o errors. I can open any table in the SQL 7 Query Analyzer and query fine. When the app tries to open a table I get:

Object #nnn (Table 'tablename'): Invalid primary key property. Validate database.

If a table didn't originally have a PK defined when it was upsized, it's ok, but any table with an original PK gives this message and tells me to validate the database.

I deleted the pk in SQL Enterprise Manager but still get the error back on the client side. When I look at the table using Design Table | Table and Index Properties, there is nothing unusual.

How do I find what property is invalid?

TIA</FONT></I>


 
©2000 Bob Archer
<-- Prior Message New Search Next Message -->