By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,889 Members | 1,373 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,889 IT Pros & Developers. It's quick & easy.

Access 2003 doing VERY WEIRD things

P: n/a
My boss and I both have access 97 and access 2003 installed on our
systems.

Lately he has been having a lot of problems. Databases that won't
close. The database looks like it closes but access will not. And
other weird things...I just passed it off as just MS nothing new.

Yesterday I asked him to look at a little project...nothing much of
anything. I put it up on our server and he opened it and went into
design view. Its a form with 1 tab and one subform. It looked like he
was in access 97 design view. Where you have a white box for the
subform with the name of the form in the upper left.. He double
clicked on it and it opened in a new window just like the old 97
version. WTheck...then he closed the database but access refused to
close. After a lot of work in task manager it finally killed it. Well
I went back to my desk and without thinking I opened the database on
the network he had just opened. WOW now I am seeing all the weird
stuff on my system too....things like I have never seen before.
I shutdown rebooted and then opened the file I had copied up to the
server that are now giving me problems....the original one on my
system is fine.
I got an idea and opened a new database and imported all the tables
and forms from the one on the server and it works fine as well..

WHAT does he have on his system that is doing this?
I looked and he has windows xp service pack 2 ....office 2003 with all
service packs and updates. system has antivirus and spybot running.
We are behind a firewall, and I have never seen any problems as far as
malicious hackers on our networks.

Has anyone seen a mess like this and have any idea what can be done to
try and fix this?

==================
ps he has tons of registered and paid for programs running on his
system.
He is a control and records freak.
Palm phone interfaced into exchange, bluetooth headsets for this and
conferencing and tons of aps for record keeping...nothing hacked or
pirated.
==================
I would not think this was a problem but I wanted to mention it
THANKS BIG TIME for reading this mess
and hope someone has some ideas

Oct 5 '06 #1
Share this Question
Share on Google+
12 Replies


P: n/a
Hello!

All I can say is that it didn't work out very well to have two different
versions of Access on my system (XP Pro, Office 2003), too.

As soon as I dumped one version, everything was quite allright again.

I don't think this is really helpful to you, but it's the only experience I
have concerning this problem.

Regards,

Michael

"sparks" <js******@swbell.netschrieb im Newsbeitrag
news:av********************************@4ax.com...
My boss and I both have access 97 and access 2003 installed on our
systems.

Lately he has been having a lot of problems. Databases that won't
close. The database looks like it closes but access will not. And
other weird things...I just passed it off as just MS nothing new.

Yesterday I asked him to look at a little project...nothing much of
anything. I put it up on our server and he opened it and went into
design view. Its a form with 1 tab and one subform. It looked like he
was in access 97 design view. Where you have a white box for the
subform with the name of the form in the upper left.. He double
clicked on it and it opened in a new window just like the old 97
version. WTheck...then he closed the database but access refused to
close. After a lot of work in task manager it finally killed it. Well
I went back to my desk and without thinking I opened the database on
the network he had just opened. WOW now I am seeing all the weird
stuff on my system too....things like I have never seen before.
I shutdown rebooted and then opened the file I had copied up to the
server that are now giving me problems....the original one on my
system is fine.
I got an idea and opened a new database and imported all the tables
and forms from the one on the server and it works fine as well..

WHAT does he have on his system that is doing this?
I looked and he has windows xp service pack 2 ....office 2003 with all
service packs and updates. system has antivirus and spybot running.
We are behind a firewall, and I have never seen any problems as far as
malicious hackers on our networks.

Has anyone seen a mess like this and have any idea what can be done to
try and fix this?

==================
ps he has tons of registered and paid for programs running on his
system.
He is a control and records freak.
Palm phone interfaced into exchange, bluetooth headsets for this and
conferencing and tons of aps for record keeping...nothing hacked or
pirated.
==================
I would not think this was a problem but I wanted to mention it
THANKS BIG TIME for reading this mess
and hope someone has some ideas

Oct 5 '06 #2

P: n/a
just tried this on his system.
We have a monster access 97 database on the server.
He copied it down to his local machine.
He clicked on the db and it opened in 2003...it said do you
want to convert or just open it.
He chose to open..
after it ran he tried to close it and the dabase closed but
access would not quit.
After killing it and opening it again ....well it looked like access
97 again...the tabs and borders around the sub forms is white
(of course it could be the lcd he is using) but mine all look the same
color as the background....his background and tabs are a different
color.
So a perfectly good database that has run for years on the server with
5 different people using it...is trash on his system..

I think his system is trash and should be formatted and reinstalled.

He SCREAMED that he has all his stuff installed and does not want to
do that.

I just walked away.
Oct 5 '06 #3

P: n/a
sparks wrote:
just tried this on his system.
We have a monster access 97 database on the server.
He copied it down to his local machine.
He clicked on the db and it opened in 2003...it said do you
want to convert or just open it.
He chose to open..
after it ran he tried to close it and the dabase closed but
access would not quit.
After killing it and opening it again ....well it looked like access
97 again...the tabs and borders around the sub forms is white
(of course it could be the lcd he is using) but mine all look the same
color as the background....his background and tabs are a different
color.
So a perfectly good database that has run for years on the server with
5 different people using it...is trash on his system..

I think his system is trash and should be formatted and reinstalled.

He SCREAMED that he has all his stuff installed and does not want to
do that.

I just walked away.

I'd scream too. Maybe ask him to open it from Explorer from a desktop
shortcut or else from a desktop icon. There you can specify the Access
version in the properties.
Oct 5 '06 #4

P: n/a
sparks wrote:
Has anyone seen a mess like this and have any idea what can be done to
try and fix this?
Yes. When I hit the close button, it just minimized in the task bar and kept
running till I killed the process.
WTheck...then he closed the database but access refused to
close.
Look in your code for all the DAO recordsets. Do they all have code that
explicitly closes the recordset and then sets the variable to Nothing before
the variable goes out of scope? Is it *always* guaranteed to close and be
set to Nothing in an error handler? Access 97 will hang if you don't take
care of this.

Look in your code for all the database objects. Do they all have code that
explicitly sets the variable to Nothing before the variable goes out of scope?
Is it *always* guaranteed to be set to Nothing in an error handler? Access
97 will hang if you don't take care of this.

Look in your code for all the checkboxes. Do you have something like this:

If Me.CheckboxName Then

instead of this?

If Me.CheckboxName = True Then

That first syntax will make it hang, too.

You mentioned in another post that your boss's tab colors and application
background colors are different than yours. There are 64K colors and your
boss changed some of his system colors from the default battleship grey to a
color less blah. (That, or his system is using LCD colors.)

I'd check for these things before I'd rebuild his system. You'll make him
very happy if you discover it's the developer's fault and fix the code
instead of wiping his computer.

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

Oct 5 '06 #5

P: n/a
On Thu, 05 Oct 2006 17:15:59 GMT, "Granny Spitz via AccessMonster.com"
<u26473@uwewrote:
>I'd check for these things before I'd rebuild his system. You'll make him
very happy if you discover it's the developer's fault and fix the code
instead of wiping his computer.

the problem is he is as close to a genius as you can come. And a lot
of these databases are his creations...Its just that in the last 3-4
weeks everything he touches goes bonkers.

I had a 97 database that people were using with no problems, they
called him and had him look at it, and he opened it in 2003, a few
days later the calls started, I can't close the database...whats
wrong?

Later it was some code that was in the database that was working fine
would no longer do what it was supposed to do. The errors were NOT
every time you tried it, but every 10-12 times it would not work
correctly.

You can't get it to do it every time so its hard to pinpoint..
he tried today to open the database that was causing problems
yesterday.

After a reboot he opened the database, it looked like a 97 again.
closed it without going to any design views, and it closed and reopen
it and its fine.
BUT he only tried what I described...he never opened any code windows.
IF he does it goes bonkers.

MAN this is weird
Oct 5 '06 #6

P: n/a
sparks wrote:
On Thu, 05 Oct 2006 17:15:59 GMT, "Granny Spitz via AccessMonster.com"
<u26473@uwewrote:

>>I'd check for these things before I'd rebuild his system. You'll make him
very happy if you discover it's the developer's fault and fix the code
instead of wiping his computer.

the problem is he is as close to a genius as you can come. And a lot
of these databases are his creations...Its just that in the last 3-4
weeks everything he touches goes bonkers.

I had a 97 database that people were using with no problems, they
called him and had him look at it, and he opened it in 2003, a few
days later the calls started, I can't close the database...whats
wrong?

Later it was some code that was in the database that was working fine
would no longer do what it was supposed to do. The errors were NOT
every time you tried it, but every 10-12 times it would not work
correctly.

You can't get it to do it every time so its hard to pinpoint..
he tried today to open the database that was causing problems
yesterday.

After a reboot he opened the database, it looked like a 97 again.
closed it without going to any design views, and it closed and reopen
it and its fine.
BUT he only tried what I described...he never opened any code windows.
IF he does it goes bonkers.

MAN this is weird

Maybe /decompile, compact, then recompile the code.
Oct 5 '06 #7

P: n/a
+ 1 for all these responses. OP, check for these things and get back to
the group.

Granny Spitz via AccessMonster.com wrote:
sparks wrote:
Has anyone seen a mess like this and have any idea what can be done to
try and fix this?

Yes. When I hit the close button, it just minimized in the task bar and kept
running till I killed the process.
WTheck...then he closed the database but access refused to
close.

Look in your code for all the DAO recordsets. Do they all have code that
explicitly closes the recordset and then sets the variable to Nothing before
the variable goes out of scope? Is it *always* guaranteed to close and be
set to Nothing in an error handler? Access 97 will hang if you don't take
care of this.

Look in your code for all the database objects. Do they all have code that
explicitly sets the variable to Nothing before the variable goes out of scope?
Is it *always* guaranteed to be set to Nothing in an error handler? Access
97 will hang if you don't take care of this.

Look in your code for all the checkboxes. Do you have something like this:

If Me.CheckboxName Then

instead of this?

If Me.CheckboxName = True Then

That first syntax will make it hang, too.

You mentioned in another post that your boss's tab colors and application
background colors are different than yours. There are 64K colors and your
boss changed some of his system colors from the default battleship grey to a
color less blah. (That, or his system is using LCD colors.)

I'd check for these things before I'd rebuild his system. You'll make him
very happy if you discover it's the developer's fault and fix the code
instead of wiping his computer.

--
Message posted via http://www.accessmonster.com
Oct 5 '06 #8

P: n/a
sparks wrote:
the problem is he is as close to a genius as you can come. And a lot
of these databases are his creations.
Oy veh! You can't tell him to blame it on the developer then.
I had a 97 database that people were using with no problems, they
called him and had him look at it, and he opened it in 2003
If he's a developer, *why* is he opening an Access 97 database in Access 2003?
He knows it has to be enabled (or converted to Access 2K+), which will affect
it when it's opened later in Access 97, sometimes adversely. It's better not
to take a chance. You can prevent this from happening you know. Go back to
a stable backup of the Access 97 MDB file and convert it to an MDE file. Put
this on the network server as the production version of the front end that
all the users copy to their hard drives. He *can't* open it in Access 2003.
And for stability, MDE files should be used for production anyway.

Actually, from your descriptions, it sounds like everyone is sharing the
front end (or maybe it's not even split?), and your boss's *enabling* Access
97 databases in Access 2003 is being felt by everyone else because they're
sharing the *same* file on the network, instead of having their own front end.
If this is what's happening, *please* don't tell me he's making changes to
the shared file while other people are using it. That bad habit usually ends
up in a disaster. Fortunately, Access 2000 and newer databases won't allow
changes to the design unless the user can open the file exclusively.
Later it was some code that was in the database that was working fine
would no longer do what it was supposed to do. The errors were NOT
every time you tried it, but every 10-12 times it would not work
correctly.
I've had this happen in plenty of applications. Every ten to twenty times or
so, the code's logic would travel down a certain branch where there was
either a logic error or the effects of a missing "Option Explicit" would come
into play, and we'd experience something inexplicable in the application, at
least until I figured out it was a bug in the code. To help you track this
down, you may want to do some more testing to determine what the
circumstances are *before* the error occurs. First thing to check for is
that Option Explicit is declared in every module. Make sure the code
compiles, too.
After a reboot he opened the database, it looked like a 97 again.
closed it without going to any design views, and it closed and reopen
it and its fine.
BUT he only tried what I described...he never opened any code windows.
IF he does it goes bonkers.
Check the references. Make sure it uses DAO 3.51, not DAO 3.6. And make
sure if there are any other Office references, they're only for Office 8.0
applications, not Office 11.0 applications.

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

Oct 5 '06 #9

P: n/a

I checked the database and it has
vb for applications
ms access 11 obj library
dao 3.6 obj library
ole automation
vb for applications extensibility 5.3 << wth is this ???
On 5 Oct 2006 11:59:44 -0700, ju*********@gmail.com wrote:
>+ 1 for all these responses. OP, check for these things and get back to
the group.

Granny Spitz via AccessMonster.com wrote:
>sparks wrote:
Has anyone seen a mess like this and have any idea what can be done to
try and fix this?

Yes. When I hit the close button, it just minimized in the task bar and kept
running till I killed the process.
WTheck...then he closed the database but access refused to
close.

Look in your code for all the DAO recordsets. Do they all have code that
explicitly closes the recordset and then sets the variable to Nothing before
the variable goes out of scope? Is it *always* guaranteed to close and be
set to Nothing in an error handler? Access 97 will hang if you don't take
care of this.

Look in your code for all the database objects. Do they all have code that
explicitly sets the variable to Nothing before the variable goes out of scope?
Is it *always* guaranteed to be set to Nothing in an error handler? Access
97 will hang if you don't take care of this.

Look in your code for all the checkboxes. Do you have something like this:

If Me.CheckboxName Then

instead of this?

If Me.CheckboxName = True Then

That first syntax will make it hang, too.

You mentioned in another post that your boss's tab colors and application
background colors are different than yours. There are 64K colors and your
boss changed some of his system colors from the default battleship grey to a
color less blah. (That, or his system is using LCD colors.)

I'd check for these things before I'd rebuild his system. You'll make him
very happy if you discover it's the developer's fault and fix the code
instead of wiping his computer.

--
Message posted via http://www.accessmonster.com
Oct 5 '06 #10

P: n/a
I'm not sure if your response is intended for Jeremy or me, but I'll respond
anyway.
I checked the database and it has
vb for applications
ms access 11 obj library
dao 3.6 obj library
ole automation
vb for applications extensibility 5.3
Then it's *not* an Access 97 database. Either it started out as an Access
2003 database, or it's been converted to Access 2003 from an earlier version.
vb for applications extensibility 5.3 << wth is this ???
A code library for manipulating the VB project. Look at the classes in the
VBIDE library in the object browser if you want specifics.

Did you check the code for DAO recordsets, databases, and check boxes?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

Oct 5 '06 #11

P: n/a
"Granny Spitz via AccessMonster.com" <u26473@uwewrote in
news:6751c1f402124@uwe:
Look in your code for all the checkboxes. Do you have something
like this:

If Me.CheckboxName Then

instead of this?

If Me.CheckboxName = True Then

That first syntax will make it hang, too.
Other alternatives that work:

If Me!Checkboxname.Value Then

If (Me!Checkboxname) Then

I prefer the latter, myself.

(the issue of . vs. ! is irrelevant to this question)

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Oct 5 '06 #12

P: n/a
sparks <js******@swbell.netwrote in
news:vt********************************@4ax.com:
I checked the database and it has
vb for applications
ms access 11 obj library
dao 3.6 obj library
ole automation
vb for applications extensibility 5.3 << wth is this ???
As you've already been told, this is clearly not an A97 database at
this point.

You should try removing the last two references and attempting a
COMPILE ALL. I've seen tons of A2K+ MDBs with those references in
them and they were not used for anything at all.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Oct 5 '06 #13

This discussion thread is closed

Replies have been disabled for this discussion.