Wierd Post migration form behaviour

Moderators: Phil Winkler, Graham Smith, Pete Tabord

Wierd Post migration form behaviour

Postby Adrian Jones » Tue Jul 16, 2013 4:19 pm

Don't know what is causing this, but thought I'd get it documented in case someone else comes across this.

I have migrated a DfW app to Ff, and the catalog shows what I'd expected to be defining forms translated into forms, and using forms into aspects.

However, there's a set of now aspects that all use the same form/table. When I make a change to them and save them, they jump back to the form list -- although the QBM dialog shows that they all share the same underlying table.

If I delete them from the forms list, I get an error that the document can't be found, although it has now left that list (and fortunately not deleted the underlying table as far as I can see).
User avatar
Adrian Jones
 
Posts: 2000
Joined: Tue Sep 11, 2007 2:38 pm
Location: Cornwall, UK
Has thanked: 5 times
Been thanked: 4 times
 

Re: Wierd Post migration form behaviour

Postby Adrian Jones » Wed Jul 17, 2013 8:47 am

I think what I am seeing is this:

In DfW, there are several non-defining forms, which as expected migrate to aspects in Ff, at least as far as the catalog/app objects is concerned.

However, there must be a flag in the document itself that thinks it is a form, and any changes to the document result in it moving 'back' to the form list.
User avatar
Adrian Jones
 
Posts: 2000
Joined: Tue Sep 11, 2007 2:38 pm
Location: Cornwall, UK
Has thanked: 5 times
Been thanked: 4 times
 
 

Return to Migration

Who is online

Users browsing this forum: No registered users and 1 guest