This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I am using lightspeed to access an old database with the associtated legacy issues. I am running into difficulty using associations because of this.
My main table is CREATE TABLE [dbo].[AccData]( ClaimId is the PKey. Claim used to be the PKey and is still a unique index
I want to associate it to CREATE TABLE [dbo].[ProcessLogs](
I want to do an association on Claim == Reference but these doesn't seem to be any way of choosing the linking field on AccClaim.
Am I missing something, or is this not possible?
Thanks
Sean |
|
|
This is not currently possible (another customer has asked for it and it is on the wishlist, but it hasn't made the cut yet). Instead, what you can do is create your own properties or methods for traversing the association, e.g. partial class ProcessLog { and conversely for the one-to-many association in the reverse direction. Note some care may be required when modifying the association -- it should just be a matter of updating the Reference FK but some caution may be required if the Claim value of an AccData can change over time. Also LightSpeed will not automatically wire up new associated entities to the unit of work, so you will need to call Add and Remove explicitly where appropriate. |
|
|
+1 on the request. I have about 30 associated table with this problem :( Put it in v3 :) Thanks
Sean |
|