Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
Reply
Silver Contributor
Posts: 835
Registered: ‎03-24-2009

Continued Duplicate Grid Refreshes.....Hello?

<RANT>

 

Just ran into this beauty that has been around for a decade.....

 

        grdContacts.RecordSet = objRS
        grdContacts.Refresh

 

Yes, that's a demi-tasse cup (a half cup cup) or Picacho Peak (Peak Peak).

 

(and yes this should be SET grdContacts.RecordSet = objRS).

 

The above double work, double round trip query is still not as popular as:

 

        grdContacts.SQL.TEXT = MyComplexSQLStatement
        grdContacts.Refresh

 

Which is like

A=6

A=6

 

Time for another cup of coffee.....

</RANT>

RJ Samp
Gold Super Contributor
Posts: 3,087
Registered: ‎03-19-2009

Re: Continued Duplicate Grid Refreshes.....Hello?

This was over in Opp - right?

--
RJ Ledger - rjledger@rjlSystems.net +1 603.369.3047 x101
alt
".. Innovators in Mobility - Experts in Workflow Automation..."
http://www.rjlSystems.net - blog: www.rjlSystems.net/blog.html
Silver Contributor
Posts: 835
Registered: ‎03-24-2009

Re: Continued Duplicate Grid Refreshes.....Hello?

Yes sir, System:Insert Opportunity non databound  form Contacts

Also non databound form SystemSmiley Frustratedelect Contact(s) INIT subroutine.

RJ Samp
Silver Contributor
Posts: 835
Registered: ‎03-24-2009

Re: Continued Duplicate Grid Refreshes.....Hello?

And another one.....this one first crops up in 7.0000 or maybe in the 6.2 stuff.......that's like 7+ years ago.

 

Sub AXFormOpen(Sender)    

      UpdateNotes

End Sub

 

Sub AXFormChange(Sender)    

     UpdateNotes

End Sub

 

500 History Records that aren't Database Changes and SalesLogix will dutifully fill the Notes Forms' Memo field....TWICE.

That's double work. And yes, both Events are wired into the form.

 

 

RJ Samp
Silver Contributor
Posts: 835
Registered: ‎03-24-2009

Re: Continued Duplicate Grid Refreshes.....Hello?

OK a new one for me......I usually set the grid to Sortable = True at design time in the Architect. That means the Query Returns all rows:

a) multiselects of grid rows across pages are CORRECT

b) Caption Header sorts are allowed.

Now that the Caption Header sorts are RecordSet Sorts (YEA!!!) instead of round trips to the server this is even better!

So on a custom entity\custom forms a developer said

Gridname.Sortable = True

 

at runtime.

 

this was returning LOTS of rows, that had nothing to do with the current SQL Statement in the grid and the correct 'LinkID'\'BindID' like AccountID = '" & gstrAccount & "' " kinds of stuff.

 

11,000 rows in three queries from three different forms.

 

Removed the statements from the AXFormChange and the 11,000 rows worth of queries disappeared.

These only showed up when the Entitiy was being manuevered to (MainView Detail kind of Jump) or an F5 was issued.

 

Like I said, a new one for me.

RJ Samp