between forms

achen · Jul 21, 2000

I have say 2 forms: A and B.  Form A is a data entry screen.  From form A, I can click push button and go to form B.  In form B, I have a list of information for users to select.  My questions are: (1) I have a DONE push button in form B.  What code should I put in the click method of the DONE push button in form B, so when the user click it they can (1)go back to form A with all the information they type in previously, (2) transfer the information selected in form B to form A, and (3)let form B disappear?? Thanks.

BlindPete · Jul 21, 2000

*switching forms... in click event oFormNameA.WindowSate = 1 && minimized oFormNameB.WindowSate = 0 && normal oFormNameB.SomeControl.Setfocus() ***assumes neither is modal and both are in screen You might consider using the tab control. Put both forms in one form, your users select the tab they want to be in. To transfer info between forms... you can pass parameters to the init event, use public variables, or add properties to each form and reference them, I have even used a cursor before.   The simplest method is to use is probably public variables but it can will be a nightmare to debug later and I don't recommend it.  Which to choose really depends on how the forms are used, closed and called. <a href=mailto:blindpete@mail.com>blindpete@mail.com</a> <a href= > </a>

BlindPete · Jul 21, 2000

On second thought... Why use two forms or tab controls at all.  Use a combo box to list the options for data entry. <a href=mailto:blindpete@mail.com>blindpete@mail.com</a> <a href= > </a>

simo · Jul 21, 2000

I create objects, say for a customer, and then create properties which are form objects.  This way, all properties and methods of all form objects belonging to the customer object, say, are accessible to every other object belonging to the customer object(including the customer object itself). e.g. this.text1.value = this.parent.formb.text1.value where parent is the customer object. customerObject_o         ¦         ----forma                ¦                ----forma properties and methods         ¦         ----formb                ¦                ---formb properties and methods         ¦         ¦         ---customer object properties         ¦         ¦         ---customer object methods I find this approach makes sharing data easy throughout the application.

BlindPete · Jul 21, 2000

What a clever approach!  Do you ever have performance problems with large apps?  IE windows starts augmenting ram with the hdrive?  Just curious... <a href=mailto:blindpete@mail.com>blindpete@mail.com</a> <a href= > </a>

JDurbin · Jul 21, 2000

Simo, How are you scoping the form objects to the cust object? This.cForm1=? This.oForm2=? Thanks looks good John Durbin <a href=mailto: john@johndurbin.com> john@johndurbin.com</a> <a href=

http://www.johndurbin.com>

</a> ICQ #9466492 
ICQ VFP ActiveList #73897253

simo · Jul 22, 2000

Performance: starting the application and closing down the application I do find is slower than normal, however, once the application has opened I find that because forms are already initialised as objects they pop up on the screen extrememly fast. I also open all my tables at the start of the app and keep them open, thus eliminating having to wait for foxpro to open the tables everytime I want to perform an operation on them. ok - this is how my application is layed out, people may think what a daft method but it works for me and is easy and quick to create once you have the initial templates set up. 1. entity objects, i.e. customer, supplier, invoices, orders, etc. 2. data access objects ¦ -----record object ¦ -----field object 3. interface objects(forms saved as classes) I create a customer object say, which can contain data access objects for as many tables as it uses. Data access objects are passed a table name, opens the table and creates a record object, and field objects for each of the fields in the table (the record object is essentially just a skeleton to hold the fields in place). So, if i had just one customer table(for this example), I would do the following command: this.addObject('recordObject','customerRecordObject_o') Once this is done, I can reference the data in the table indirectly, i.e. if i wanted to get the customer reference I would do this: ref = this.customerRecordObject_o.custRef.value (custref is a field object which is a property of the record object). I can save and restore using the following method: this.customerRecordObject_o.pop() && gets data to mem this.customerRecordObject_o.push() && commits data to disk one field would be: this.customerRecordObject_o.custRef.pop() this.customerRecordObject_o.custRef.push() I also have record locking methods also. In the main entity object I also have lots of search and find code to remove me from the table-level operations and thus prevent (easy to make) mistakes such as moving a record passed EOF, typing GOOT instead of GOTO, etc - I never actually issue this command anymore. To add form classes to the entity object(in this case customer) I do something similar to this: this.addObject('mainCust_frm','mainCustForm_o') Therefore text boxes, etc on the form objects can be assigned to my data objects, i.e.: thisform.custRef_txt.controlSource = ; thisform.parent.customerRecordObject_o.custref.value I think that I will get kicked off if I take too much more space in this thread soon

All my entity objects are also members of the main application object(thisapp), therefore every single object can be accessed down a hierarchy making sharing data and methods easy - but it can get messy if it is not managed properly, methods should still be assigned to the correct objects, I try not to have any code apart from validation on my forms, and have all the main processing code in the entity objects, I find that this makes forms much faster and smaller. The downside, is of course, that all my code is stored in one class library, so if this goes wrong - no, I won't think about that, that's what backups are for

If you are interested an want to know more about how I do things then let me know.

JDurbin · Jul 22, 2000

Have you read VFP 6 Enterprise by Paddock & Peterson.  You may find their enterprise classes interesting.  I'm just reading it now John Durbin <a href=mailto: john@johndurbin.com> john@johndurbin.com</a> <a href=

http://www.johndurbin.com>

</a> ICQ #9466492 
ICQ VFP ActiveList #73897253

Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

between forms

achen

Programmer

BlindPete

Programmer

BlindPete

Programmer

simo

Instructor

BlindPete

Programmer

JDurbin

Programmer

simo

Instructor

JDurbin

Programmer

Similar threads

Part and Inventory Search

Sponsor