Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Double hit on NewID()
Message
 
To
24/09/2001 10:59:55
Jason Mesches
Ocean Systems Engineering Corporation
Carlsbad, California, United States
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Miscellaneous
Thread ID:
00559921
Message ID:
00559996
Views:
21
Found it. Thanks. The primary key was changed and I failed to follow up with the updateable change.
Jon

>We've run into this early and often...
>
>1st check - Make sure you're view's primary key field is marked as updateable. For some reason, it's default setting is not updateable.
>
>2nd check - If you're running Stonefield, make sure you aren't pulling in default values from your table into views ("View field property inheritance" is the name of the setting). Otherwise, the view will cause NewID() to fire automatically, and then the framework will fire it again when it's trying to populate the PK field. I think Kevin fixed that piece of code in the framework to check the value in the field first to make sure it's blank before running NewID() again, but that all depends on which version of Mere Mortals you have.
>
>---J
>
>>I'v run into this sometime ago, too long to remember and with the search down at UT, my memory is down as well.
>>
>>I have subclassed cBizObjNoListMaintForm when I create a new record (pressing Add command button), NewId issues a new unique ID as expected, but it is hit again upon saving creating the second instance. lAutoNewRecord is .f. and the bizobj's lUIEnablerNewRecord is .f.
>>
>>Any help would be appreciated.
>>Thanks
>>Jon
Previous
Reply
Map
View

Click here to load this message in the networking platform