11-20-2013 06:51 AM
Just ran into this beauty that has been around for a decade.....
grdContacts.RecordSet = objRS
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
Which is like
Time for another cup of coffee.....
11-20-2013 08:30 AM
11-20-2013 12:54 PM
And another one.....this one first crops up in 7.0000 or maybe in the 6.2 stuff.......that's like 7+ years ago.
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.
11-27-2013 02:07 PM
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
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.