I had a similar problem and found that the "Off" in the customErrors Mode tage was case sensitive.
I.E.
<customErrors mode="Off" />
works, but
<customErrors mode="off" />
doesn't.
Hope this helps
Yep. The problem was that I thought I was storing a long but was actually storing the recordset field object in the collection. I think the XP environment is a little less forgiving about default properties vs. object references.
I do think that VB's error trapping could be a shade more robust...
Whoops, Sorry I didn't notice the year, and thought it was only a week old :-)
Thanks, it could be a related issue for me - although I (think I) am only storing a long in the collection, I am pulling it from a recordset so I may be storing a reference to the recordset, but I don't think so -...
Not a solution, but a similar problem with collections ...
I have a VB6 app on XP which also happens to be using MDI forms (I don't know if this matters).
I have declared a collection at form Module level and then destroy and recreate it as necessary. I add some (or one) items using a key...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.