Access 2003 upgrade.

J

James Lee

I have just upgraded from Access 2000 to 2003 and find I cannot get an
application which ran perfectly well to run on 2003. It seems to be a
very similar problem to that which was raised in a thread by Fritz
Anton dated 4/12/2003 which ran to some twelve articles but which did
not seem to come to any real solution despite a couple of responses
from Microsoft.

A macro in the VB code is used to reset the Visible property. It is
conditioned by the property itself so that that it is called only if
"Yes" and changed to "No".

When it tries to run the macro in the VB code an error is generated
saying "The object you referenced in the VB procedure as an OLE object
isn't an OLE object."

Jet 4.0 SP8 has been installed.

I can't find any FAQ etc to help, has anyone any ideas?

James Lee.
 
J

Jeff Conrad

Uhhhh Ken, clicking on the link you provided gives me this:

"The content you have selected is available only to MVPs. If you are an MVP, please sign in using
the Microsoft® .NET Passport associated with your MVP account. If you are not an MVP, please select
from the navigation links on the left."
:)

James, try this link to read the article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;841916
 
J

Jeff Conrad

Well I tried logging in as AccessJunkie, but no luck.
;-)

(Heading out of town, talk with you later)
 
J

James Lee

Thank you for your responses, I have been temporarily off this project
but have now returned to it.

I have been unsucccessful with the workround as suggested in Article
ID 841916. I did not really hold out much hope for it since I found a
FAQ about Access Security Warnings which specifically warns that the
RunCode macro action cannot be used to call a VBA procedure.

I also found that the SetValue action also doesn't work for the
Enabled property.

While I have been able to produce a workround by substituting VBA code
for the macros this is going to be a lengthy procedure to change the
affected macros in the application and leaves me with an uncomfortable
feeling about which further properties and/or actions may be affected.

For peace of mind, it is far easier just to set the sandbox security
to low or to go back to 2002.

Which begs the question - Do I have any less security when running
2002 compared with running 2003 with low sandbox security.

This is a small but business critical application for the organisation
concerned and runs on a four terminal in-house network with no
connections to the web or other outside world institutions.

I would be very grateful for any comments or suggestions, best regards

James Lee
 
K

Ken Snell [MVP]

James Lee said:
Which begs the question - Do I have any less security when running
2002 compared with running 2003 with low sandbox security.
Click to expand...


I may be wrong, but I believe that the security level is essentially the
same between A2K2 and "low sandbox security" in A2K3.
 
J

Jeff Conrad

Top