<i><font color="#663300">Boy, I don't know what cornfield I have been hiding out in but the primary key retrieval apparatus that I have been using low these many months is failing. The disturbing thing is that I don't know why it ever did.
DataBhavior.SetNewPK uses CURSORGETPROP() to retrieve the table underlying the current view. It passes this value to GetNextLocalPK() which uses "!" to parse the DBC name out of it. The only problem is that CURSORGETPROP doesn't return the tablename prefixed with the DBC, so when GetNextLocalPK uses DBGETPROP to retrieve the default value, it gets nowhere.
I just upgraded to W2K and reinstalled everything. Is there a setting that tells VFP to prefix the table with the database? Why did this used to work?</font></i>
Pamela,
This happened me long ago with an early version of xCase which did not appropriately prefix the tables with their DBC name. How did you generate your DBC? You might want to look deeper at its content with a utility like GENDBC or GENDBCX.
José
Jose Constant
Constant Software Systems
Belgium
<a href=http://www.constant.be/css target=_blank>Jose's Web Site</a>
©2001 Jose Constant |
