B
BurntBird
I'm working with a new setup and have encounted the following.
We are using Terminal Services to connect to a Win 2003 server with a dual
core processor and running Access 2003. When ever we run anything slightly
complex in Access, it slows right down and in some cases appears to hang.
Following method 1 in Kb178650, as soon as we set the msaccess process
affinity to only one processor it comes back to life and works great.
I find it odd that access 2003 doesn't seem to have issues on my local pc
which also has a dual core but is running XP sp2 (and isn't via TS).
1. What else should I look into or is possibly an issue?
1. Is the issue TS, Access, or both?
2. Since I am using msjet40 not msjet35 is there a fix?
3. If no fix, is there a workaround other than manually or using vba code to
change the process affinity?
Thank you so much for any help!
We are using Terminal Services to connect to a Win 2003 server with a dual
core processor and running Access 2003. When ever we run anything slightly
complex in Access, it slows right down and in some cases appears to hang.
Following method 1 in Kb178650, as soon as we set the msaccess process
affinity to only one processor it comes back to life and works great.
I find it odd that access 2003 doesn't seem to have issues on my local pc
which also has a dual core but is running XP sp2 (and isn't via TS).
1. What else should I look into or is possibly an issue?
1. Is the issue TS, Access, or both?
2. Since I am using msjet40 not msjet35 is there a fix?
3. If no fix, is there a workaround other than manually or using vba code to
change the process affinity?
Thank you so much for any help!