ScottCybak
Programmer
Hello, i've been developping in acess 2000 since i began, and yesterday i installed XP - what a wonderfull upgrade, my mouse scroll works in listboxes, and most importantly, the OpenReport method supports opening arguments and the modal property.
Now, this database will be ran on 2000 versions as well, and i'm trying to create an optimized print sub routine, as i have a custom print dialog that i display. The sub routine uses:
If SysCmd(7) = 10 Then
'Code for XP version
Else
'Code for 2000 version
End If
To diffentiate the version used (this does work properly on access xp), BUT, if i open this in 2000, i get compile errors whenever i run the code.. and it freezes on my OpenReport line
Basically, i thought the compiler would skip this, as the version is 9 in 2k and it skips this due to the If statement, but it obviously doesn't.
The module was option explicit, but i removed it hoping that perhaps it would compile - no deal. There are about 10 computers running 2K and only 2 on XP.. how can i fix this? I search this and a few other sites, including the MSKB to no avail.
TIA Scott Cybak
scott@athree.com
Now, this database will be ran on 2000 versions as well, and i'm trying to create an optimized print sub routine, as i have a custom print dialog that i display. The sub routine uses:
If SysCmd(7) = 10 Then
'Code for XP version
Else
'Code for 2000 version
End If
To diffentiate the version used (this does work properly on access xp), BUT, if i open this in 2000, i get compile errors whenever i run the code.. and it freezes on my OpenReport line
Basically, i thought the compiler would skip this, as the version is 9 in 2k and it skips this due to the If statement, but it obviously doesn't.
The module was option explicit, but i removed it hoping that perhaps it would compile - no deal. There are about 10 computers running 2K and only 2 on XP.. how can i fix this? I search this and a few other sites, including the MSKB to no avail.
TIA Scott Cybak
scott@athree.com