Thursday, September 11, 2003
New Update to Foxfire! COM Component
Added some new functions to Foxfire! COM component to make it easier for getting objects and collections in DotNet.
If you are familiar with the FF! object model, you'll know that each object has the Items collection. Requests have collections for DataItems, Sorts, Calculations , etc and so on.
Apparently, DotNet in all its inherent omniscience can't grab one of these collections properly so we created GetRequests() which simply returns the Requests collection.
Now to get an item, you actually have to call GetItem( ).
So the code would look something like this:
x = CREATEOBJECT("foxfireom.ffapplication")
? x.setlocation("\ff60ent\")
lo = x.GetRequests()
loReq = lo.GetItem(1)
? loReq.RequestName
? loReq.Description
loItems = loReq.GetDataItems()
? loItems.count
? x.setlocation("\ff60ent\")
lo = x.GetRequests()
loReq = lo.GetItem(1)
? loReq.RequestName
? loReq.Description
loItems = loReq.GetDataItems()
? loItems.count
Oh well....
Separate download available: http://www.foxfirereporting.com/livedesign/ffom.zip
Email support@micromegasystems.com for the password.
Comment
Wednesday, September 10, 2003
New updates available
A new update is available online at http://www.foxfirereporting.com/livedesign/ff80.zip.
This update saves the user preference for how the Request Editor is configured. So if you roll-it up to see the entire live design surface area, it saves this preference for the next time you login.
This is done with the new GetUserPref and SetUserPref settings in the object model.
Speaking of which, the latest documentation for the object model can be viewed here: http://www.foxfirereporting.com/livedesign/om.doc
Enjoy!
Comment
Tuesday, September 09, 2003
New Update Posted - Better Sorting Options
Fixed a few things with this update, including
- Sort Header no longer shows if no sorts are displayed
- Group options dialog (under Sort/Group) is only enabled for grouped sort items. This dialog now properly updates the Request preview.
- The Style is now correctly selected after creating a new request. In previous versions, if you tried to create a new request and then went into an existing one, the sort on RPT_STYLE was incorrect and as a result, the request did not load properly.
More to come....
Comment
