Vista problem?

[Dudley]

I have a database which runs OK on my work XP computers but I cannot work on
it at home because it will not run on my home Vista computer.

Several command buttons will not work on my home computer. I get error

Run time error '-2147352567(8002009)':
You can't assign a value to this object

on

Dim stDocName As String
Dim stLinkCriteria As String

stDocName = "Minutes"
stLinkCriteria = "[EnvelopeNumber]=" & Me![EnvelopeNumber]
DoCmd.OpenForm "Minutes", , , stLinkCriteria
[Forms]!Minutes.EnvelopeNumber = Me.EnvelopeNumber

Yet this works on the XP computers. I have checked that they have the same
references.

Another problem is that when I close the database I often cannot open it
again because the lock file has not closed. Checking Task Manager, the
problem appears to be that Access sometimes fails to close in Processes, even
though it is closed in Applications. I do not have the same problem with
other databases. Compact and Repair solves this problem, but it soon comes
back. It appears to be some corruption in the database which only affects it
on my Vista computer.

Any suggestions?

Thanks
Dudley

 

[Jack Leach]

I do the vast majority of my development on a Vista Home Premium system for
an app that runs across XP and NT, and have not experienced any of these
issues. Therefore I can suggest that this is a problem not directly stemming
from Vista, but rather in some sort of (like you said) db corruption, or
possibly a lack of proper updates to applications (OS and Office). I would
start by making sure you have all current updates, and it may be a good idea
to try importing into a new db. I would assume a fresh db may do the trick.
You may want to find an area of the problem code and transfer just this
portion into a new db to test on your vista platform.

After a few years developing on Vista and deploying to XP, the only thing
I've noticed different is a) vista has a tighter control of file security,
and b) a few APIs (one or two that I've found) return false information with
Vista. But as far as normal everyday code, everything should be working
correctly.

hth
--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)

 

[Gina Whipp]

Dudley,

There are several things I would check...

1. Try right mouse click and Run as Administrator.
2. What version of Access? If 2007, is it in a Trusted Location?
3. Do you have this problem with any database you run or just this one? If
all, then how was Access installed, as Administrator?
4. Have you installed ALL your updates?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

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

I do the vast majority of my development on a Vista Home Premium system for
an app that runs across XP and NT, and have not experienced any of these
issues. Therefore I can suggest that this is a problem not directly
stemming
from Vista, but rather in some sort of (like you said) db corruption, or
possibly a lack of proper updates to applications (OS and Office). I
would
start by making sure you have all current updates, and it may be a good
idea
to try importing into a new db. I would assume a fresh db may do the
trick.
You may want to find an area of the problem code and transfer just this
portion into a new db to test on your vista platform.

After a few years developing on Vista and deploying to XP, the only thing
I've noticed different is a) vista has a tighter control of file
security,
and b) a few APIs (one or two that I've found) return false information
with
Vista. But as far as normal everyday code, everything should be working
correctly.

hth
--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)

I have a database which runs OK on my work XP computers but I cannot work
on
it at home because it will not run on my home Vista computer.

Several command buttons will not work on my home computer. I get error

Run time error '-2147352567(8002009)':
You can't assign a value to this object

on

Dim stDocName As String
Dim stLinkCriteria As String

stDocName = "Minutes"
stLinkCriteria = "[EnvelopeNumber]=" & Me![EnvelopeNumber]
DoCmd.OpenForm "Minutes", , , stLinkCriteria
[Forms]!Minutes.EnvelopeNumber = Me.EnvelopeNumber

Yet this works on the XP computers. I have checked that they have the
same
references.

Another problem is that when I close the database I often cannot open it
again because the lock file has not closed. Checking Task Manager, the
problem appears to be that Access sometimes fails to close in Processes,
even
though it is closed in Applications. I do not have the same problem with
other databases. Compact and Repair solves this problem, but it soon
comes
back. It appears to be some corruption in the database which only affects
it
on my Vista computer.

Any suggestions?

Thanks
Dudley

 

[Dudley]

Thanks to both of you for your advice and I will follow up your suggestions.
I have Access 2000, and I have seen the idea of running as administrator
before, but right clicking does not give me this option. I only have the
problem with one database, and only the front end.

Thanks
Dudley

Dudley,

There are several things I would check...

1. Try right mouse click and Run as Administrator.
2. What version of Access? If 2007, is it in a Trusted Location?
3. Do you have this problem with any database you run or just this one? If
all, then how was Access installed, as Administrator?
4. Have you installed ALL your updates?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

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

I do the vast majority of my development on a Vista Home Premium system for
an app that runs across XP and NT, and have not experienced any of these
issues. Therefore I can suggest that this is a problem not directly
stemming
from Vista, but rather in some sort of (like you said) db corruption, or
possibly a lack of proper updates to applications (OS and Office). I
would
start by making sure you have all current updates, and it may be a good
idea
to try importing into a new db. I would assume a fresh db may do the
trick.
You may want to find an area of the problem code and transfer just this
portion into a new db to test on your vista platform.

After a few years developing on Vista and deploying to XP, the only thing
I've noticed different is a) vista has a tighter control of file
security,
and b) a few APIs (one or two that I've found) return false information
with
Vista. But as far as normal everyday code, everything should be working
correctly.

hth
--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)

I have a database which runs OK on my work XP computers but I cannot work
on
it at home because it will not run on my home Vista computer.

Several command buttons will not work on my home computer. I get error

Run time error '-2147352567(8002009)':
You can't assign a value to this object

on

Dim stDocName As String
Dim stLinkCriteria As String

stDocName = "Minutes"
stLinkCriteria = "[EnvelopeNumber]=" & Me![EnvelopeNumber]
DoCmd.OpenForm "Minutes", , , stLinkCriteria
[Forms]!Minutes.EnvelopeNumber = Me.EnvelopeNumber

Yet this works on the XP computers. I have checked that they have the
same
references.

Another problem is that when I close the database I often cannot open it
again because the lock file has not closed. Checking Task Manager, the
problem appears to be that Access sometimes fails to close in Processes,
even
though it is closed in Applications. I do not have the same problem with
other databases. Compact and Repair solves this problem, but it soon
comes
back. It appears to be some corruption in the database which only affects
it
on my Vista computer.

Any suggestions?

Thanks
Dudley

.

 

[Dudley]

I am now getting the same problems on the XP copies, so it is clear that the
only solution is to revert to an earlier version of the database and re-do
the work I did on it.

Thanks for your help.
Dudley

Thanks to both of you for your advice and I will follow up your suggestions.
I have Access 2000, and I have seen the idea of running as administrator
before, but right clicking does not give me this option. I only have the
problem with one database, and only the front end.

Thanks
Dudley

Dudley,

There are several things I would check...

1. Try right mouse click and Run as Administrator.
2. What version of Access? If 2007, is it in a Trusted Location?
3. Do you have this problem with any database you run or just this one? If
all, then how was Access installed, as Administrator?
4. Have you installed ALL your updates?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

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

I do the vast majority of my development on a Vista Home Premium system for
an app that runs across XP and NT, and have not experienced any of these
issues. Therefore I can suggest that this is a problem not directly
stemming
from Vista, but rather in some sort of (like you said) db corruption, or
possibly a lack of proper updates to applications (OS and Office). I
would
start by making sure you have all current updates, and it may be a good
idea
to try importing into a new db. I would assume a fresh db may do the
trick.
You may want to find an area of the problem code and transfer just this
portion into a new db to test on your vista platform.

After a few years developing on Vista and deploying to XP, the only thing
I've noticed different is a) vista has a tighter control of file
security,
and b) a few APIs (one or two that I've found) return false information
with
Vista. But as far as normal everyday code, everything should be working
correctly.

hth
--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)



:

I have a database which runs OK on my work XP computers but I cannot work
on
it at home because it will not run on my home Vista computer.

Several command buttons will not work on my home computer. I get error

Run time error '-2147352567(8002009)':
You can't assign a value to this object

on

Dim stDocName As String
Dim stLinkCriteria As String

stDocName = "Minutes"
stLinkCriteria = "[EnvelopeNumber]=" & Me![EnvelopeNumber]
DoCmd.OpenForm "Minutes", , , stLinkCriteria
[Forms]!Minutes.EnvelopeNumber = Me.EnvelopeNumber

Yet this works on the XP computers. I have checked that they have the
same
references.

Another problem is that when I close the database I often cannot open it
again because the lock file has not closed. Checking Task Manager, the
problem appears to be that Access sometimes fails to close in Processes,
even
though it is closed in Applications. I do not have the same problem with
other databases. Compact and Repair solves this problem, but it soon
comes
back. It appears to be some corruption in the database which only affects
it
on my Vista computer.

Any suggestions?

Thanks
Dudley

.

 

[Gina Whipp]

Did you try refreshing the links as in Vista the lik path is different.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

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

Thanks to both of you for your advice and I will follow up your
suggestions.
I have Access 2000, and I have seen the idea of running as administrator
before, but right clicking does not give me this option. I only have the
problem with one database, and only the front end.

Thanks
Dudley

Dudley,

There are several things I would check...

1. Try right mouse click and Run as Administrator.
2. What version of Access? If 2007, is it in a Trusted Location?
3. Do you have this problem with any database you run or just this one?
If
all, then how was Access installed, as Administrator?
4. Have you installed ALL your updates?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors
II

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

I do the vast majority of my development on a Vista Home Premium system
for
an app that runs across XP and NT, and have not experienced any of
these
issues. Therefore I can suggest that this is a problem not directly
stemming
from Vista, but rather in some sort of (like you said) db corruption,
or
possibly a lack of proper updates to applications (OS and Office). I
would
start by making sure you have all current updates, and it may be a good
idea
to try importing into a new db. I would assume a fresh db may do the
trick.
You may want to find an area of the problem code and transfer just this
portion into a new db to test on your vista platform.

After a few years developing on Vista and deploying to XP, the only
thing
I've noticed different is a) vista has a tighter control of file
security,
and b) a few APIs (one or two that I've found) return false information
with
Vista. But as far as normal everyday code, everything should be
working
correctly.

hth
--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)



:

I have a database which runs OK on my work XP computers but I cannot
work
on
it at home because it will not run on my home Vista computer.

Several command buttons will not work on my home computer. I get error

Run time error '-2147352567(8002009)':
You can't assign a value to this object

on

Dim stDocName As String
Dim stLinkCriteria As String

stDocName = "Minutes"
stLinkCriteria = "[EnvelopeNumber]=" & Me![EnvelopeNumber]
DoCmd.OpenForm "Minutes", , , stLinkCriteria
[Forms]!Minutes.EnvelopeNumber = Me.EnvelopeNumber

Yet this works on the XP computers. I have checked that they have the
same
references.

Another problem is that when I close the database I often cannot open
it
again because the lock file has not closed. Checking Task Manager, the
problem appears to be that Access sometimes fails to close in
Processes,
even
though it is closed in Applications. I do not have the same problem
with
other databases. Compact and Repair solves this problem, but it soon
comes
back. It appears to be some corruption in the database which only
affects
it
on my Vista computer.

Any suggestions?

Thanks
Dudley

.