12:16:30 AM
3I300L87V
I will do so, I can get a lot to work but some issue need either a different approach or recoding in the base application wich is not always bad.
Fore instance, took you wwait example and ported the whole application thru a similar process i.e. created a mgr_wait class where all wat window stuff goes thru. This resulted in that faa only needed to adapt one statement. OOP and OOP again. Most stuff is pretty OOP based so i am running into some issues with that.
We use a lot of factory stuff
For instance: I have the base class std_tab
This class gets fed in some parameters and sets up a tabular grid for the table passed ect ect.
All our basetables i.e products. departments,groups ect ect are all shown on opening in a tabular manor
We use free tables and only open them JIT i.e. just in time
Setting up works but it seems that FAA relies on the actuall newly created object to exist as a class when doing row changes ect ect
I can understand that from a stateless point of view but it would mean creating a lot of new classes based on the baseclass.
Any ideas
examples
object = thisform.wform("std_tab",.f.,"groups_prc") -> creates a new object with the name groups_tab
gets shown on browser ect ect but when doing rowchanges it complains about object group_tab not being available
Due to the stateless situation faa wants to run the code thru groups_tab but for some reason does not seem to find it
Any ideas if all of this makes sense.
Theo
Could be nice to post back when you find a workaround and/or a valuable suggestion.
my $.02
Hello Thierry,
Should have come back earlier,
Managed to solve this issue by a matter of deduction ;-)
