Valentina error #529669 with V4RB_25b23_macho

[Stan Busk]

Yes, that did he trick! Well done! Seems it was a duplicate link  
name, reason why it failed on second ObjetPtr declaration.

Thanks,
Stan

> Hello Stan,
>
> Thursday, November 30, 2006, 6:39:00 PM, you wrote:
>
>> I have tried a lot of things and finally I think Ivan has made all
>> that too strict. It is so strict you can no longer create ObjectPtr
>> Fields thru a schema update because (for a reason I don't know) it
>> never matches the class definition...
>
> No, we need such strict checks for "Static way" (Class way).
> Especially with ObjectPtrs.
>
> Look - the link name in ObjectPtr declared as optional. If you skip it
> then  system  will choose the link name self. But it is NO GUARANTY it
> will be unique one.
> So it is always a good idea to mention link name self.
>
> Open  your  database with Valentina Studio and see what the link
> name   is  stored  for  that  ObjectPtr (it is really stored name even
> if you did not mention it self). Then correct your "static way"
> ObjectPtr definition using this name as link name for the ObjectPtr.
>
>
> Also, it is highly recommended to choose some meaningful link name  
> - not
> a just "Link_1".
>
>
> -- 
> Best regards,
>  Ivan                            mailto:ivan_smahin at valentina-db.com
>
> _______________________________________________
> Valentina-beta mailing list
> Valentina-beta at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina-beta