I have a Vista Ultimate machine running Access 2007; this hardware
previously ran XP Pro with Access 2003. Now that I've upgraded, I've
found that I can't use even small Access MDBs that are stored on a
network share, while the same MDBs copied to local storage seem fine
(although slower than I remember with the old setup).

These MDBs are still in 2003-format, and don't seem to have any problem
being opened on the same network with XP/Acc2003 or even XP/Acc2007.
Clearly, I think my issues are Vista-related.

Although I'd love someone to respond with "here's how you fix it", I'd
be happy enough to find out that others are having the problem and that
MS is trying to figure it out.

My share is a Windows 2000 Server (SP4a) that is a domain (Windows
2003-native) member, and I have full permissions to the share and the
volume/files.

i don't want to sound dumb.. but how in the hell can you have a
windows 2003 native network on windows 2000?

just had to ask




On Apr 10, 6:52 pm, Jim Millard wrote:
I have a Vista Ultimate machine running Access 2007; this hardware
previously ran XP Pro with Access 2003. Now that I've upgraded, I've
found that I can't use even small Access MDBs that are stored on a
network share, while the same MDBs copied to local storage seem fine
(although slower than I remember with the old setup).

These MDBs are still in 2003-format, and don't seem to have any problem
being opened on the same network with XP/Acc2003 or even XP/Acc2007.
Clearly, I think my issues are Vista-related.

Although I'd love someone to respond with "here's how you fix it", I'd
be happy enough to find out that others are having the problem and that
MS is trying to figure it out.

My share is a Windows 2000 Server (SP4a) that is a domain (Windows
2003-native) member, and I have full permissions to the share and the
volume/files.

On Apr 10, 9:47 pm, "
wrote:

My share is a Windows 2000 Server (SP4a) that is a domain (Windows
2003-native) member, and I have full permissions to the share and the
volume/files.

i don't want to sound dumb.. but how in the hell can you have a
windows 2003 native network on windows 2000?

just had to ask

Because a Windows 2003 Native domain only requires that the servers
responsible for the AD be Windows 2003, not all the members of the
domain. I don't think he said anything about the Windows 2000 Server
being anything other than a file server.

wrote:
On Apr 10, 9:47 pm, "
wrote:
My share is a Windows 2000 Server (SP4a) that is a domain (Windows
2003-native) member, and I have full permissions to the share and the
volume/files.
i don't want to sound dumb.. but how in the hell can you have a
windows 2003 native network on windows 2000?

just had to ask

Because a Windows 2003 Native domain only requires that the servers
responsible for the AD be Windows 2003, not all the members of the
domain. I don't think he said anything about the Windows 2000 Server
being anything other than a file server.


You are correct. Active Directory is a database, and the schema versions
have changed with the updates from NT4-compatible domains to
2003-native domains.

he's trying to give as complete a picture as possible of the way file
sharing is handling security on his network; the 2003-native domain also
implies that he's using IP (instead of IPX or netbeui; not likely but
possible).