Hi

I have a refresh dilema where I launch a form from a button, fill in some details on the form, close the form (saving the data) which then takes me back to the original form. This works okay and the data is saved, however there is a field on the original form that is also on the updated form which still shows the old entry until I come out of the original form and go back in where you can then see the updated value.

I presumed i'd be able to refresh this field using the standard refresh functions but they don't seem to work. I need the form to refresh when the updated form is closed (click Ok), can I somehow refresh the original form when closing another form?

I hope i've made sense....!!

Any advice would be appreciated.

Thanks

Dave

What is the script\function\line of code you are using for the launching of the form?

Do you have an AXFormChange subroutine and a databound field for the 'base' table on the base form?

What version of SalesLogix?

Rather than DoInvoke - use Application.BasicFunctions.ShowViewForRecord (pass in "" if you want a new ID) but, in essence, if you have this:

Form A - DataBound to data that displays Data then

FormB is invoked from a button/script from FormA that somehow affects the data on Form A then this will not automatically update Form A

If you had:

Main View -> Form A -> Update - then MainView would change

But, if you have:

Main View -> Form A -> Form B -> Form C - then any updates that happen on Form C (or B) won't reflect in Form A - you'd have to modify them yourself... (based on the return of the form).

Regards
Mike

Here is another way you might do it.

Use your OnCreate of the base form to capture a reference to the form

Dim oForm

Sub AXCreate(Sender)

  set oForm = Sender

I assume you are launching your other forms via script, so at the end of your script

oForm.Refresh

will get your base form to refresh.

ws

1. Mike's suggestion to use ShowViewForRecord includes an automagic refresh of the form that the call is made from.....it's not in the documentation but it does a RefreshMainView every time (if you have a valid AXFormChangeScript.

2. you need an ID field, hidden, on your base form, for the base ID (AccountID, ContactID). That guarantees the AXFormChange.

3. In the AXFormChange, place a call to your grid refresh routine.

4. If you don't have a grid refresh routine, use SLX Profiler and see how many times you actually are firing off the grid refresh (duplicately!!). I've posted numerous times up here about using BINDID, SQL.Text = , having a :BINDID clause in the SQL statement for the grid, using Grid.Refresh, etc. ALL of which fire off the grid refresh.

5. Lookups will refresh on a form refresh, no problem there.....see Opportunity.Account if you don't think so....but you must have a valid AXFormChange and you must use ShowViewForRecord.

and all of this works properly in 7.2.2.

Walter's method works as well, but no need for it if you use ShowViewForRecord which includes the oForm.Refresh and the .RefreshMainView. That's how SLX changes the Opportunity Detail's Sales Potential when you edit the Opportunity Products tab OppProduct record on the popoup data form.