Huge problems - Access 2003 SP3 on Server 2008.

[ThomasAJ]

I have just set up w2008, installed Office 2003 with SP3, latest updates all
round.
All references are correct, Access compiles.

In many many places I get a 'Function is not available in expressions in
query expression...'. It seems to not like the Format function.

These expressions have worked fine for years.

There are also many other problems - like graphs not running - list boxes
not being filed (probably related to the query issue above).

One more crazy issue - a simple text box had ControlSource = Date().
The '=Date()' is completely missing on W2008. When I go to put it in I get a
"the Function you entered can't be used in this expression"

I hope I have overlooked something simple.

 

[John W. Vinson]

In many many places I get a 'Function is not available in expressions in
query expression...'. It seems to not like the Format function.

This appears to be the very common References bug. Open any
module in design view, or open the VBA editor by typing
Ctrl-G. Select Tools... References from the menu. One of the
..DLL files required by Access will probably be marked
MISSING. Uncheck it, recheck it, close and open Access.

If none are MISSING, check any reference; close and open
Access; then uncheck it again. This will force Access to
relink the libraries.

 

[david]

This looks like an extreme case of sandboxing, so may be something new
with Server 2008, except that I would have thought some one would have
noticed it before now.

Of course, not many install Office on a server, so I could be wrong. Is this
a Terminal Services Server?

Have you tried changing the Access security settings?

http://support.microsoft.com/kb/239482

As you may know, all of the VBA words that can be used in a Query are
listed in a VBA JET dll. Most of these are 'safe' functions, and can be
used in sandbox mode. There are a few that are not safe, a few that just
got forgotten, and a few that are in the cracks between the other
categories.

So it is possible that Jet 4 on Server 2008 has a broken implementation
of 'safe' and just doesn't allow VBA in queries.

But you should also try (again) making an MDE on the server, in case
you were tired or distracted last time you tried to compile....

(david)

 

[ThomasAJ]

Thanks for the post. I am travelling at the moment and will try your
suggestion/s within 48 hrs.

 

[ThomasAJ]

Thanks for the post. I am travelling at the moment and will try your
suggestion/s within 48 hrs.

--
Regards
Tom

This looks like an extreme case of sandboxing, so may be something new
with Server 2008, except that I would have thought some one would have
noticed it before now.

Of course, not many install Office on a server, so I could be wrong. Is this
a Terminal Services Server?

Have you tried changing the Access security settings?

http://support.microsoft.com/kb/239482

As you may know, all of the VBA words that can be used in a Query are
listed in a VBA JET dll. Most of these are 'safe' functions, and can be
used in sandbox mode. There are a few that are not safe, a few that just
got forgotten, and a few that are in the cracks between the other
categories.

So it is possible that Jet 4 on Server 2008 has a broken implementation
of 'safe' and just doesn't allow VBA in queries.

But you should also try (again) making an MDE on the server, in case
you were tired or distracted last time you tried to compile....

(david)

 

[ThomasAJ]

Yes it turned out to be related to 'References' and to only 1 of them
(MSSOAP30.DLL) even though the 'huge problems' were totally unrelated to the
functionality provided by MSSOAP30 - go figure.

Note - there were no 'missing' references. I zeroed in on MSSOAP as I did
have problems with this DLL a long time ago and thought I'd give
unchecking/checking a try on this one. Instant gratification!

Many thanks John.

 

[ThomasAJ]

While your suggestion did not apply in this case (it was a DLL reference bug)
I really appreciate your very detailed suggestions. Thanks David.
--
Regards
Tom

This looks like an extreme case of sandboxing, so may be something new
with Server 2008, except that I would have thought some one would have
noticed it before now.

Of course, not many install Office on a server, so I could be wrong. Is this
a Terminal Services Server?

Have you tried changing the Access security settings?

http://support.microsoft.com/kb/239482

As you may know, all of the VBA words that can be used in a Query are
listed in a VBA JET dll. Most of these are 'safe' functions, and can be
used in sandbox mode. There are a few that are not safe, a few that just
got forgotten, and a few that are in the cracks between the other
categories.

So it is possible that Jet 4 on Server 2008 has a broken implementation
of 'safe' and just doesn't allow VBA in queries.

But you should also try (again) making an MDE on the server, in case
you were tired or distracted last time you tried to compile....

(david)