inStrRev Problems

  • Thread starter Thread starter KML via AccessMonster.com
  • Start date Start date
K

KML via AccessMonster.com

I create a report that uses the inStrRev function in A2K. It works fine on my
PC and another. But one of the user's PC is not cooperating at all. When the
report is run on his machine, it prompts for inStrRev as if it's a Parameter.
I checked his References and made sure he has the same ones I have. And it
still didn't work. I did a repair of his Access and still no luck. I did a
uninstall/reinstall of Office 2K, but to no avail. Next I tried just doing a
Windows XP Upgrade and it still doesn't recognizes the inStrRev function. I'm
running out of options here. I'm thinking of wiping out his PC and doing a
fresh install of XP and Office 2K. But thought I checked with all you gurus
on here first before I do that. Any suggestions?
 
While I know you said you checked the references, it sure sounds like a
References problem to me.

If none of the selected references have "MISSING:", select an additional
reference at random, back out of the dialog, then go back in and unselect
the reference you just added. If that doesn't solve the problem, try to
unselect as many of the selected references as you can (Access may not let
you unselect them all), back out of the dialog, then go back in and reselect
the references you just unselected. (NOTE: write down what the references
are before you delete them, because they'll be in a different order when you
go back in)
 
Is the offending PC running the same verison of windows with the same service
packs installed and the same version of Access with the same service packs
installed?
 
Douglas said:
While I know you said you checked the references, it sure sounds like a
References problem to me.

If none of the selected references have "MISSING:", select an additional
reference at random, back out of the dialog, then go back in and unselect
the reference you just added. If that doesn't solve the problem, try to
unselect as many of the selected references as you can (Access may not let
you unselect them all), back out of the dialog, then go back in and reselect
the references you just unselected. (NOTE: write down what the references
are before you delete them, because they'll be in a different order when you
go back in)


I never used A2k, so I'm real vague about this, but isn't
InStrRev one of the functions that A2K only reconized in
VBA? And wasn't there an SR that rectified the problem??
 
Marshall Barton said:
I never used A2k, so I'm real vague about this, but isn't
InStrRev one of the functions that A2K only reconized in
VBA? And wasn't there an SR that rectified the problem??

Like you, I never used Access 2000, so I'm not sure. I thought it was only
Replace that had problems.

However, the OP did state that it worked on his/her computer, just not on
another.

Like you, Klatuu may have hit on it, though when he asked whether the
offending machine was on the same service pack.
 
Yes, the list of problem functions includes:
FormatCurrency(),
FormatDateTime(),
FormatNumber(),
FormatPercent(),
InStrRev(),
MonthName(),
Replace(),
Round(),
StrReverse(),
WeekdayName()

Source:
http://support.microsoft.com/?id=225956

It's hard to pin down the issue here. I recently had a client strike a
problem with Replace(). The MDB works fine on my copy of Access 2000, but
failed on his. He had Office 2000 SP3 and JET 4 SP8, so I don't know why it
failed on his.
 
We gave up and put the User Defined Functions
back in for InStrRev and Replace. We had a
development machine here in the office that
couldn't use Replace, and if we unexpectedly
got the problem here in the office, it didn't
look good for deployment to clients.

Notice that InStrRev is not listed as either
'blocked' or 'safe in sandbox mode':

How to configure Jet 4.0 to prevent unsafe functions from running in Access
2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;294698&Product=acc


Clearly InStrRev cannot be used in Jet sandbox mode:
(?) But Access Sandbox Mode is supposed to control
Jet Sandbox mode.(?)

Perhaps there is an installation or registration
problem, or perhaps there is something about sandbox
mode.

(david)

Allen Browne said:
Yes, the list of problem functions includes:
FormatCurrency(),
FormatDateTime(),
FormatNumber(),
FormatPercent(),
InStrRev(),
MonthName(),
Replace(),
Round(),
StrReverse(),
WeekdayName()

Source:
http://support.microsoft.com/?id=225956

It's hard to pin down the issue here. I recently had a client strike a
problem with Replace(). The MDB works fine on my copy of Access 2000, but
failed on his. He had Office 2000 SP3 and JET 4 SP8, so I don't know why
it failed on his.
 
Thanks to all for your responds and ideas!
I've tried all the suggestions and that PC still have the same issue. I
believe something wasn't setup correctly when it was built. I tried to do a
Windows Update and that kept hanging on one of the patches. So I'm going to
have our PC guy rebuild it. I'll let you know how that turns out.
Thanks again.
 
Back
Top