[AccessD] Search with Ctrl+B freeze app

Hi William

No, that is not so. Access 97 is installed the normal way and the FE in a directory of its own.
Only the desktop icon is provided by the profile.

My colleague suggests that "something" could have been installed on her machine which caused "something" to Access and/or her profile which then is carried around if she logs in on other machines ...

Quite vague thoughts as you can see.

Oh, and Groundhog Day is one of my favourite movies!

/gustav

>>> wdhindman at bellsouth.net 16-11-2005 13:28 >>>
...is the mdb somehow being placed in her local profiled directories and 
uploaded to her server profile on the server?
...I'd look in her server profile and see if the notwork guy has got the mdb 
directory as one of her profile caches.
...this of course assumes that her local copy of the fe was corrupted in the 
first place, seen by the server as a change when she logged off, and then 
uploaded to her profile cache to forever repeat ...groundhog day, eh :)

...if this turns out to be the case, I'd Colbyize the notwork guy :(

William
----- Original Message ----- 
From: "Gustav Brock" <Gustav at cactus.dk>
To: <accessd at databaseadvisors.com>
Sent: Wednesday, November 16, 2005 6:20 AM
Subject: [AccessD] Search with Ctrl+B freeze app


> Hi all
>
> Have anyone experienced issues when using Ctrl+B to open the search form?
>
> A client has a user with an Access 97 app which has run for years.
> Suddenly, if she presses Ctrl+B to search it works fine but next time she 
> does this, the app freezes and becomes inactive. She has to reboot or use 
> Task Manager to kill Access.
>
> The tricky part is that if other users log in on her machine, the issue 
> persists. Other users don't see this issue when working at their own 
> machine. However, if the user in question logs in on another user's 
> machine, the issue follows her.
>
> The client uses roaming profiles and the notwork guy claims to have 
> rebuilt these but to no avail.
>
> My own guess is to double-check for some corrupted Access/Jet temp files 
> as the first thing.
> Before reinstalling "everything" I wonder if anyone has seen something 
> similar?
>
> /gustav