2K/XP recordset/library

[RoyVidar]

I have two questions conserning using the same app on different versions of Office (XP and 2000 (2K))

When programming, I have a tendency to use the same recordset variable thru the whole snippet, opening and closing it, just using different sql-strings, cursortype, locktype etc

That works nicely in my version of Office XP, but withouth SP1, at least, or in Office 2K, the program halts at the rs.open statement and laconicaly explains "Errors occured".

By just declaring and using a second recordset (rs2) it's running as it should.

BTW - it doesn't help to close and "set rs=nothing", it simply has to be a new recordset variable.

Ideeas?

Next question - I develop in XP (saving as 2K), and in one App I use a reference to the Microsoft Office Library (doing some toolbar stuff).

When i recreate the base (after all the bluescreens and "Sorry for the inconvenience", and MSACCESS /Decompile doesn't work) in XP, it never works in 2K, stating Missing or invalid reference... When created in 2K, I can move them between versions without any trouble at all.

Ideas?

 

[DaltonVB]

When i recreate the base (after all the bluescreens and "Sorry for the inconvenience", and MSACCESS /Decompile doesn't work) in XP, it never works in 2K, stating Missing or invalid reference... When created in 2K, I can move them between versions without any trouble at all.?

I noticed this when working in OfficeXP and deploying the database to Office 2000 users. Access upgrades your libraries for you when you are in design view of a form or report. What I did was created it in XP and publish from Access 2000 on another machine with the same MDAC and other libraries as my users.