Can't move the focus to the control (repeat request)

[IanC]

Sorry for the repeat request, but my newsgroup provider failed to forward
any messages between 05:56 on 5 Jan and 21:46 on 8 Jan. My original post was
at 17:21 on 5 Jan.

Since my original post I've found a workaround and that it to put the image
on a command button. This is far from ideal and would really like to get to
the bottom of what's happening.

I've searched online for a solution, but all the solutions I've found so far
refer to errors in code. There isn't any code in the form itself, just
several command buttons with attached macros.

Original post follows:

I've just had a new laptop. The first thing I did was to get everything up
to date from the MS website (Windows and Office).

When I try to open a local copy of our company database, I get the message
"Microsoft Access can't move the focus to the control Image19".

I realise that an image can't receive the focus, but I didn't have (and
still don't have) this issue on my old laptop. I'm still using Access 2000,
so this isn't the problem. The only thing I can think of that is different
is that I've applied XP SP3 to the new laptop, whereas the old one is still
on SP2.

Are there any known issues of compatibility between Office 2000 and Windows
XP SP3? I've not come across anything else causing problems (not that I've
done much on this laptop yet).

I've tried removing/reinstalling Office (after trying the repair and
reinstall options).

Any ideas?

Ian

 

[MikeJohnB]

Do you need the image to take focus on opening the form?

If not, why not put an unbound textbox with zero width on the form adjacent
to the image and in the on open event of the form.

Me.TextBoxname.SetFocus

Because the textbox has zero width, you cant see it but because it is not
hidden, it can accept focus.

If I have mis-understood the issue, please forgive

Kindest regards

Mike B

 

[IanC]

Hi MikeJohnB

No, I don't need the focus on the image.

The form is called by the Autoexec macro consisting of 3 commands -
OpenForm, Maximize, GoToControl (which points to a command button).

If I step through the macro, I can see that when the GoToControl command is
executed, the target command button is briefly selected before apparently
losing focus when the error appears.

The issue is that it only does it on my new machine. It still works
perfectly on 50+ other PCs including my old laptop and some running Vista.
I'm not sure whther anyone else is using XP Sp3, hence my question about
compatibility.

I suspect your solution wouldn't work as I don't really see a significat
difference between using GoToControl in the macro and SetFocus in the form
open event.

I'd really like to get to the bottom of this without having to get the main
database changed at head office (when I download my local copy from). Our IT
department is aware of the problems I'm having, but as the IT deparment
consists of 1 person and she's got more than emough on her plate already....

Any further thoughts would be most welcome.

Ian

 

[MikeJohnB]

Mmmmm,

I see why you are reluctant to change anything on the main database but I
wasn't aware you were using the Macro. No, the solution of moving focus on
load or open in the form wont do anything because the macro has already fired.

At the moment, I am not aware of any issues with SP3 for XP but that is
mainly because I haven't yet loaded it on the company laptop. I have to do
that on Monday so I might be looking at solutions as well come Tuesday.

I will however do a little research later today.

the only other thing I can think of is to goto a different control in the
macro but as you don't want to change the database, that doesn't really help.

I have also found that in the main, IT people know very little about the
actual applications. They are more into the management of the systems. I
don't want to say that all are the same, just what I have found in my field.

If I come across anything else, I will post back.

Kindest regards and Hope you sort the issue soon.

Mike B

 

[IanC]

Hi Mike

I finally figured out what the problem was. It was nothing to do with XP SP3
or Access itself!!

My new laptop is an HP. It came with something called "Credential Manager"
which allows for login details etc to be stored and applied automatically
when an application or web page is opened.

If I am logged into Credential Manager, the problem occurs, even though I
wasn't using it to log me into the database.

All I needed to do was log out of Credential Manager and everything was OK,
but I didn't discover this until I'd wiped the hard drive and started
again!!

Frustrating really, as I was beginning to find Credential Manager useful.

Ian