Alrighty, my SQL errors are fixed. Always check your schema for reserved words! D'oh! But now I have a conundrum.
I have a table with a compositeID. One portion of that key is the foreign key for a onetomany relationship with its parent. I've tried setting it up as a m2o relationship as well, but that seems to confuse transfer. I've tried setting it up as a straight property, but that also gets things confused. I figure there are three possible scenarios: 1: This is all covered in the core docs, and when it's pointed out to me, I will feel like an idiot. 2: This is covered in the discussions here, and when it's pointed out, I will feel like an idiot. 3: This can all be handled by intelligently refactoring my schemas, in which case I will feel like an idiot. I'm already resigned to feeling like an idiot, so please belabor the obvious if you so desire... :) Ken --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
