Invalid Object Name error with function depending on user

[Guest]

We have an .adp with a menu option that runs a function. When a user tries
to run it, they get the "Invalid object name 'Foo_function'" message. When I
run it, it functions just fine. All domain users have public and db_owner
rights on the back-end database. I've given the user Admin rights to see
what would happen and it runs fine. When they're set back, it fails again.
Some research also suggested that having an underscore in the function name
could cause a problem. I'm currently testing that as well but would like to
know if anyone out there has run into this before.

 

[Michel Walsh]

Hi,


You don't mean using a (user defined or otherwise) VBA function in
T-SQL? because that does not work. Only JET ( + Access as environment) can
use VBA function in its queries.



Hoping it may help,
Vanderghast, Access MVP

 

[Van T. Dinh]

I don't have any problems using underscores in UDF names.

I think it is possible that you use some SP or in-built functions that
require access to the "System Databases" (such as "master") and hence the
problem with public / db_owner but no problems with SQL admin

 

[Guest]

Seemed to have solved my own problem. Found an article (ID : 294875) that
explains a bug regarding the stripping of underscores from functions when
called. Rather than getting our techs involved in installing service packs
(a Kafkan effort if ever there was one), I just renamed all my functions
without the underscores. The users are now able to run them properly. I
don't claim to know why an Admin wouldn't be affected by the bug ... just
that this solution works for me.