Alternative to using ExecuteSQL in a Table definition
I am getting data from a system where the structure to their table looks like this:
So If you want to know the zipcode for a Client you need to look at FieldID = 6 for that ClientID. I would like to translate this into a more "normal" table for with Client_ID, Address1, Address2, City, State, ZipCode, Country, etc. I know that I could do this with an ExecuteSQL in the field definition, but I am wondering if there is a better design with FM13Pro. Would anyone like to make a suggestion?