Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Metadata driven Wizard
Message
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Network:
Windows 2003 Server
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01443448
Message ID:
01443607
Views:
40
That's pretty much how I ended up dealing with it. Since (I think) VFP6 you've been to use the COMPILE command so needless to day that makes the task much eaiser.

>Hi Gary and Victor.
>
>An easy way to check your memo fields for errors is write a simple program that writes all the code out to a PRG file, with appropriate procedure names separating each block of code and then have VFP compile that. I've used that with meta code in the past and it's helped a lot. If you are editing the memo field with a form you've created then you can do a compilation on just a single memo each time you change it. You just erase the ERR file, do the compile, and if there is now an ERR file there were problems and you can display that to help you sort it out.
>
>Ian Simcock.
>
>
>
>>>Hi All,
>>>
>>>I am looking to develope a metadata driven set of wizard forms, the idea is that different clients can have the wizard tailored for them.
>>>
>>>I am looking to have the controls, validations, code to execute etc. all held in a metadata table.
>>>
>>>Anyone done something similair? have an pointer or ideas to include/avoid?
>>>
>>>Regards
>>>
>>>Gary.
>>
>>I've done something like this before.
>>The way I did it was to extend the .dbc using StoneField http://www.stonefield.com/ - and then mapped the fields in the database to various controls. It was a little complicated to get it to fly with comboboxes and grids - and the whole thing took me almost a year to do. In the long run it was REALLY cool though - most of the forms in the application were dynamic - and all the controls were placed an the form at runtime - so to change the app all you had to do was change the meta data. I was also able to indicate via SDT which tables were considered "lookup" tables.
>>I did put some validation code in there as well - which of course was stored in memo fields.
>>The only thing that was troublesome was the since the validation code was stored in tables, it wasn't compiled until runtime - so if there was a syntax error you didn't know it until the program was running.
ICQ 10556 (ya), 254117
Previous
Reply
Map
View

Click here to load this message in the networking platform