Hi Gary,
>However, AfterNew() is still a good place to assign the PK value, IMHO.
Are you saying you set lAutoPk to false normally? and usually use AfterNew()?
>If you set lAutoPK True on a cursor, CM automatically adds a PK using PrimaryKey (via SetPrimaryKey()) if there is no code in the DBC's default rule or in AfterNew(). However, I like to have a little more control over my PK's than that!
I do not have any code in the DBC, but I do have lAutoPK set to true. Is this a problem you think, or does CodeMine know I am setting them myself in the AfterNew()?
>Just a point on the above code though, you really would be better of using the Codemine Replace() method rather than a native VFP Replace. Codemine's replace ensures that the FieldValid and AfterChange methods are called.
Ok... I will take a look at this. I did it this way as the old 6.1 doc's had it with the regular replace I think.
Yes, I been busy... thats why I haven't been around much lately. But I'm about done. All is going well.....:)
Mel Cummings
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only