ActiveX Data Objects (ADO) enable you to access and manipulate data from a variety of different sources. Through ADO, you can connect to various databases such as Access, mySQL, PostgreSQL, MSSQL, Oracle and more. Once connected you can execute SQL against the database, as per normal.
ADO provides a series of objects, methods and properties to make your life as a developer easier. One such object is the
RecordSet, which provides a
GetRows purpose is to copy a series of records from a populated
RecordSet object and place them into an array. You can specify the number of rows to copy, where to start copying from and what fields in the
RecordSet you’d like copied. The general format is as follows:
myArray = myRecordSet.GetRows(<number of rows>, <starting position>, <fields>)
After consulting the documentation for the method on MSDN, it appears that calling the
GetRows method actually advances the current cursor position in the
RecordSet. As an example, consider a
RecordSet with the cursor position pointing to the first item. After calling
GetRows with a three (3) for the first parameter, the next time you read the
RecordSet the cursor will be pointing at the fourth record.
Unfortunately, I was caught out by this feature. Without consulting any documentation on the method first, I expected that calling
GetRows would copy an arbitrary number of records from any position in the
RecordSet without altering the current cursor position. If it did need to move the cursor to access the rows, I expected that it would return the cursor to the original position.
This is really just a fine implementation issue. I felt that since it was a copy type method, that it wouldn’t have made any modification to the
RecordSet object. If you hadn’t of read the documentation, would you expect that it would advance the cursor or leave it in its original position?
With the wedding creeping up on us week by week, it was well and truly time to organise the suits for the groom and groomsmen.
It was suggested that we first port of call be Tony Barlow, as he apparently has a good range of formal wear for weddings, formals, balls and so forth. The suggestion was spot on, we didn’t need to go anywhere else for it – they had everything we needed. Our attendant, Sonya (from memory) was also fantastic, she knew what we should and shouldn’t be wearing, what looks good and what is considered a fashion faux pas. The whole experience was very simple and straight forward, no doubt helped along by a great attendant.
Strike one more from the list, September 24 here we come!
Last night, Natalie dropped a link to a site all about coffee porn (yes, the content is work safe – except for the domain name itself). The mental imagery was running rampant to start with, picturing people making espresso in the nude and who knows what else.
Once I clicked into the site, I was given a very pleasant surprise – its a coffee site, by coffee lovers for coffee lovers, of sorts. It shows a whole bunch of close up photos of coffee being made, ie the cradle with fresh coffee and crema filtering through it. There are some really awesome shots on there actually, I really like:
I think I’ve now seen one of the most beautiful things in the world, ohh how I love coffee.
Over the weekend we had some unexpected visitors in the backyard, ducks! I was walking towards our back sliding door, when what should I see, but a pair of wild ducks waddling along in our back yard, happily quacking away. I took a couple of very quick photos before they continued to the neighbours yard.
Following on from IE7 Beta 1 receiving its first public beta release, comes more fantastic news. On the 29th July, the IE team posted again, outlining what has already been fixed in IE7 but is not present in the release they made available. For those that don’t feel like clicking through:
- Peekaboo bug
- Guillotine bug
- Duplicate Character bug
- Border Chaos
- No Scroll bug
- 3 Pixel Text Jog
- Magic Creeping Text bug
- Bottom Margin bug on Hover
- Losing the ability to highlight text under the top border
- IE/Win Line-height bug
- Double Float Margin Bug
- Quirky Percentages in IE
- Duplicate indent
- Moving viewport scrollbar outside HTML borders
- 1 px border style
- Disappearing List-background
- Fix width:auto
- HTML 4.01 ABBR tag
- Improved (though not yet perfect) <object> fallback
- CSS 2.1 Selector support (child, adjacent, attribute, first-child etc.)
- CSS 2.1 Fixed positioning
- Alpha channel in PNG images
- Fix :hover on all elements
- Background-attachment: fixed on all elements not just body
These are the sorts of fixes that the standards based development community have been screaming about for the last five years. I’m very excited to hear that in the coming months, we might be able to see the first stable release of IE7 with a vast portion of fixes in place. Lets keep those wheels rolling and squish the bugs that have plagued Internet Explorer for years.