Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Unwanted behaviour (nolistmaintform)
Message
 
To
All
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Title:
Unwanted behaviour (nolistmaintform)
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows 2000 SP3
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00973576
Message ID:
00973576
Views:
61
I have a standard form used to handle orders and order line items (parent and child). I am using the nolistmaintform as my base class form for this. The form has a tab for the child records (line items) and I use the clistobjedit container for this to add, edit and delete line items. This form works perfectly when called from the toolbar (or main menu).

I then needed to call this form from another form to edit an order since this new form listed the order number (the primary key of the order). I want to do this instead of having to launch the associated find form for this and selecting the record from the find form.

I modified my order form by changing the INIT method to accept a parameter for the primary key and then populate the pk value into the cfinduniqueid property of the order form. This works properly since it launches the form and gets the specified record correctly.

However, when I click on the add or edit buttons on the clistobjedit container for the line items and then click OK on the subsequent edit form, the program immediately asks 'Do you want to save your changes?'. And this behaviour does not happen when I launch the form through the regular means (without a primary key passed).

Is there a better way to launch this form with the pk value already known?

Any ideas or help in this matter is appreciated and Happy New Year to all!!
Reply
Map
View

Click here to load this message in the networking platform