Hi all

Here goes....

1) I have a remote database using FireBird. Don't walk away pllleeease, this has general relevance for VFP databases

2) It contains a table mAccounts

3) I have created remote views, BOs, forms and have got it working, so far so good

4) I have another table aAccounts, which contains minimum 2 fields
a) iID Integer for Unique ID's. Primary Key
b) iPID Integer for Parent ID's. Foreign Key. The Parent is mAccounts.iID

5) Later this table can have any practical number of fields of valid types (generally Char,VarChar,Int, Date, Double), but which and how many fields depends on the users requirements

6) Reason for this and such other tables is that in any and all of my apps till date, apart from the fields required by the app there are always requirements of fields which have no relevance to the app and are purely documentational and user specific bloating the database for all users. Same app another user and these fields are different. I am open to arguments on this point but am not ready to keep a seperate project, database, whatever just for the sake of user specific fields. Also have to keep the app low maintenance (low remitance so low cost). I don't mind a one time R&D to get this working, so I can standardize this for real oop/reuse in one and every app

7) This table will always have 1 to 1 relation with it's Parent mAccounts in this case

8) I have created a updateable remote view (see SQL for it below) where iID is the key and updateable and the other field iPID is updateable. BO for the same and have dropped this BO on the form for mAccounts and the forms works as before

SELECT * ;
	FROM AACCOUNTS AACCOUNTS ;
	WHERE AACCOUNTS.IPID = ?VP_IPID

9) On deployment at the users end a FlexiField is added mRemarks (VarChar 200), how to populate aAccounts is another subject, later.

10) Now start the form and it goes for a four:

Error #:    1542
Message:    Base table fields have been changed and no longer match view fields. View field properties cannot be set.
Line #:     47
Code:       DataEnvironment::OpenTables()
Method:     opentables
Object:     frmmaccounts.boaAccounts.oDELoader

11) After a few errors the form does start and when I exit it more errors (I haven't tried data-entry in this volatile stage)

12) The question is how to tackle this problem of base table fields having changed?