Access Conflict

Hello,

We have an Access 97 database residing in a shared network folder. Recently
we got new computers. The new computers are running Windows XP SP3, Microsoft
Office 2003, Compatiblitiy Pack for the 2007 Office System, Microsoft Office
Converter Pack, Microsoft Silverlight and Office 97. The original computers
run Windows XP SP2, Microsoft Office 2000, and Office 97. The database works
fine on the original computers. The new computers are a different story. When
we select a specific control in a form, a macro that is not supposed to run
on this control attempts to run. We have to halt it. This does not happen on
the original computers. Some users are using the original computers, while
others are using the new ones. Any ideas? We tried uninstalling Office 2003
and updating net framework. Any help is greatly appreciated.

Kassie

--
Message posted via http://www.accessmonster.com

"Kassie42 via AccessMonster.

Have you decompiled and recompiled the app on the new computers?

BTW, the .NET Framework has absolutely no effect on Access at all.

--
David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

David W.

I did learn that two other programs are having issues with access as well,
though they are different issues. I am guessing they are related to the image
otherwise it is a wierd coincidence. They also reside in a shared network
folder although the one program has a Windows Network established.

--
Message posted via http://www.accessmonster.com

Kassie42 wrote:One other thing, the "Title Bar" top left corner that normally

One other thing, the "Title Bar" top left corner that normally shows the key
and reads Microsoft Access now shows the key and reads Short Cut. It is not a
shortcut that I am looking at. I created a new database and tried importing
the data, etc., but still have same problem with everything.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-macros/200911/1

Kassie42,This sounds like it might have to with References.

Kassie42,

This sounds like it might have to with References.  Check for MISSING
References http://www.regina-whipp.com/index_files/References.htm

Also, as Access 97 used a different set of References then 2000, 2003 and
2007 and some are not even needed in the newer versions of Access, list the
References you do see here.  Seeing those will help us identify the ones
that no longer need.

--
Gina Whipp

II

http://www.regina-whipp.com/index_files/TipList.htm

Gina Whipp wrote:Hi Gina,I tried to get the references, but I was unable to

Hi Gina,

I tried to get the references, but I was unable to access "References" list.
Maybe because it is still in 97?  I followed the directions in the link, but
I do not get the Reference menu.

I know there is some piece missing to this puzzle.

Kassie

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-macros/200911/1

"Kassie42 via AccessMonster.

Surely you compile your code in your app, right? If not, you must be
a real novice!


I cannot say, as there is not enough information to make much of a
guess. Are these computers created by imaging a hard drive, or is
the Access installer being used to create the installation? If the
former, maybe the Access program image is corrupt or incorrectly
installed.

--
David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

Kassie,Can you get to the Design of any form?

Kassie,

Can you get to the Design of any form?  Or perhaps this Access 97 database
is an MDE file?

--
Gina Whipp

II

http://www.regina-whipp.com/index_files/TipList.htm

David W. Fenton wrote:Hi David,We are not programmers here just technicians.

Hi David,

We are not programmers here just technicians. We do not typically work too much
with access hence the problems. We also did not create the image another
department did. Believe me, we have tried to speak to a person over there and
also have a service call in, but have not gotten anywhere which is
frustrating. I think we are going to strip the computer down and start from
the basics and go from there. We already uninstalled and reinstalled access,
but that did not work, but then again we are using the access program they
provided us from the shared drive. We will need to request a clean install of
97. I appreciate everyone trying to help me and I am sorry I cannot provide
much more information.   Kassie

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-macros/200911/1

Gina Whipp wrote:Gina,I can get to the design of the form.

Gina,

I can get to the design of the form.

Kassie

--
Message posted via http://www.accessmonster.com

While in Design Mode press the Code button (colored square looking thingy...

While in Design Mode press the Code button (colored square looking thingy...
thingy = technical term).  Once in the Code window go to Tools...
References...  A window should open with objects listing in it.  Simply
write down those items which have a check check mark and type them here...
in the order in which they are typed.

--
Gina Whipp

II

http://www.regina-whipp.com/index_files/TipList.htm

Your instructions are for A2000 and after -- A97 had no seperateVBE.

Your instructions are for A2000 and after -- A97 had no seperate
VBE.

All you have to do is hit Ctrl-G and then go to the Tools menu. The
first choice is REFERENCES.

--
David W. Fenton                  http://www.dfenton.com/
usenet at dfenton dot com    http://www.dfenton.com/DFA/

David,it is been awhile since I had to use Access 97...

David,

it is been awhile since I had to use Access 97... THANKS for the correction!
I better note that on my website!

--
Gina Whipp

II

http://www.regina-whipp.com/index_files/TipList.htm

Kassie42 wrote:I have been doing some similar migrations recently:One

I have been doing some similar migrations recently:

One suggestion I have is to get into the VBA editor (ALT F11), then use the
DEBUG Menu and the Compile Option to see what ACCESS finds.  If it compiles
cleanly (I suspect it may not) then the TOOLS Reference recommendation would
seem a good next idea.

Failing both of these you can set a BREAK POINT by clicking the small left
column on the VBA code page for a convenient line near your suspicious area.
Then use the IMMEDIATE WINDOW (CTL G) and the ? Operator to examine some
variables.  In fact Mouse-overs of some of the variables should pop-up values
for you.

It sounds like you may not be too literate in VBA.  If not perhaps you could
give it a try and draw the Applications Support group in with a Q&A that way.

Maybe this will provide some direction?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-macros/200911/1