 Re: Runtime Access 2002 (I need help)running on Win2K Win98
DD wrote:[color=blue]
> I have developed a a nice little software package(Packaged with Wise
> and SageKey)
> My product works great in a clean enviroment on Win98 and Win2k and XP
> As soon as i introduce Office 2000 Pro onto either Win98 or Win2K i
> get an error on certian forms "Undefined Function DlookUp" or
> "undefined Function Nz expression".
>
> If i remove the Nz from expressions on an affending form it opens with
> out a problem.
> I however have lots of Nz in different routines and expressions
> through out the software.
>
> Do i need to go down the track of removing the Nz or can anyone
> advise.
> I have looked at my References and i can not remove any more
>
> they are
> Visual Basic for Applications
> Microsoft Access 10.0 Object Library
> Microsoft DAO 3.6
> Ole Automation
>
> I removed
> Microsoft Vusual Basic for Applications Extensibility 5.3[/color]
Tell the O2K people they're out of date and need to upgrade :-)
There's prolly some conflict with the VBA libs vis 2K vs 2K2 but I don't
have much experience of O2K as I put this down to one of the alternate
versions to skip (1 bad, 2 good, 95 bad, 97 good, 2K bad, XP good, the
stupid macro security introduced in A2K3 confirms they're sticking to
the pattern) although I understand that A2K is better now with all the
service packs (better mention that b4 I get smited by the A2K fans) so
my first suggestion would be to make sure everyone is on the latest
service packs.
I know some IT depts don't like installing latest service packs, etc.
and only install a SP to fix a specific problem but in all the sites I
visit I find those that are on the latest service packs have less
problems than those that aren't. It's not like a software publisher will
admit to 100% of the bugs they fix in service packs.
If no joy after that and no-one else comes up with anything specific and
it's only Nz you have a problem with then you might get around it by
writing your own Nz function, you may or may not have to rename the
function depending on whether it will work or not, e.g.
(air code, silly parameter names used to avoid wrapping in Usenet)
Public Function Nz(p1 As variant, Optional p2 As variant = "")
If IsNull(p1) Then
NZ = p2
Else
Nz = P1
End If
End Function
I've written my own MsgBox function called "MsgBox"[1] so there's no
problem doing that, it allows me to customise the function to my own
specs, this may benefit you or anyone else reading this as you may like
to make the default return value from Nz something different from a zero
length string, e.g. if you mostly use it on mumblers then just use
"Optional p2 As variant = 0"
[1] For anyone interested my MsgBox function is just like the original,
takes the usual parameters (including Optional ByVal plngButtons As
VbMsgBoxStyle = vbOKOnly to get intellisense) but it will make a call to
Eval() to display the message box using the Access Msgbox function
rather than the VBA one, this is because the VBA one
(Interaction.MsgBox) doesn't handle other alphabets like Cyrillic, etc.
Optionally you can throw in those @ formatting things they had in A97 as
well.
--
\\\\\\
\\ \\ Windows is searching
\ \ For your sig.
\ \ Please Wait.
\__\
| 
