MSA Runtime SP2 screwed up my App!!

[brainlord]

Help!

When users install the MS Office Access Runtime and Data Connectivity
2007 SP2 (released Apr 24) my app stops working!

The main window of my app is a Continuous forms form where each row
has several small graphics (filepath bound image controls) and a few
text fields. When the user clicks on one of these, several events fire
based on which ROW the user clicked on. After installing the SP2, when
the user clicks on any of the image controls, the events fire as if
the user has clicked on the Top row, no matter what row he clicked on.

To restate: Clicking on Image controls no longer updates whatever
value Access stores the Current Row in. (is that SelTop?) Any
references to the "Me". Object simply return the values of the record
in the Top Row.

If the user clicks on a *text* control on row X. Then it does update
the Current Row. (and row X works) but then if user clicks on an Image
control on any other row he just keeps getting results from Row X.

This is happening in the Access Runtime and in my full Access 2007.

Does MS even know about this?

Does anyone think MS will fix it? (and fast? I have users out there!)

My app can't be the only one that depends on Image controls on
Continuous forms. All of them will start acting funny.

Is it just going to be up to us to just try to code our way out this??
(As I write this I'm guessing one Code-Around would be to invisible
text controls on top of all these graphics (but there's 19 of them),
Maybe invisible buttons. (I don't know what controls will or won't
update Current Row anymore)

Now's when we need one of you MVPs to go on up the Microsoft mount,
talk to your developer contacts, and tell us what the burning bush
said.

 

[Maurice]

This might seem like a duhhh answer but why install it then? Ok you don't
know upfront that this is going to happen you are right about that. But if
the app is critical than why not uninstall it, mail for support and ask MS if
they are planning to do anything about this. If the problem is serious enough
they will create a hotfix for it.

I know not the answer you were hoping for but it's a start...

 

[Tony Toews [MVP]]

When users install the MS Office Access Runtime and Data Connectivity
2007 SP2 (released Apr 24) my app stops working!

Can you create a one or two form MDB/ACCDB file with exactly your
problem and nothing else and email it to me. tony at granite dot ab
ca. I will then send it off to Microsoft for testing purposes.

Does MS even know about this?

Almost certainly not otherwise this problem wouldn't have happened in
the first place.

Does anyone think MS will fix it? (and fast? I have users out there!)

Yes. Fast? I don't know. It will likely be at least a month or two
as it takes at least that long for fixes to make it out to the public.
Or so I've noticed in the past.

Now's when we need one of you MVPs to go on up the Microsoft mount,
talk to your developer contacts, and tell us what the burning bush
said.

Yup, that can be done. But we need that MDB/ACCDB so they can
duplicate this problem.

Tony

 

[Tony Toews [MVP]]

My app can't be the only one that depends on Image controls on
Continuous forms. All of them will start acting funny.

There might not be too many folks who use image controls directly in
that fashion. I suspect many folks would use command buttons with
images embedded in them. I use command buttons with text.

Is it just going to be up to us to just try to code our way out this??
(As I write this I'm guessing one Code-Around would be to invisible
text controls on top of all these graphics (but there's 19 of them),

Yup, that'd work. Or should work.

Tony

 

[Tony Toews [MVP]]

Help!

When users install the MS Office Access Runtime and Data Connectivity
2007 SP2 (released Apr 24) my app stops working!

The main window of my app is a Continuous forms form where each row
has several small graphics (filepath bound image controls) and a few
text fields. When the user clicks on one of these, several events fire
based on which ROW the user clicked on. After installing the SP2, when
the user clicks on any of the image controls, the events fire as if
the user has clicked on the Top row, no matter what row he clicked on.

Allen Browne has seen something similar and may jump in this thread.

Do you have the record selector visible on this continuous form? He
states that the record selector doesn't jump to the chosen record when
you click on a image control like it did pre SP2.

Tony

 

[Allen Browne]

The behavior I'm seeing is slightly different from what you describe.

The image control in A2007 has a Control Source property, so this is the
first version you could make a continuous form and display different images
shown in each record. When you click on an image, you would expect Access to
make that the current record: that's the behavior you get for other controls
that have a Control Source (text box, combo, check box, ...)

But that's not the behavior you get. Clicking an image does NOT make it the
current record. If you show the form's Record Selector, you will notice that
the current record does not change. Consequently, any code you run in the
Click event of the image control report the *current* record, not the record
that you actually clicked on.

That's the behavior you get from controls that cannot be bound (unattached
label, rectangle, ...) It is not the behavior you expect from the image
control now that it can be bound.

When A2007 was first released, the mouse events of the image control (click
etc) did not work at all. That was fixed in SP1, i.e. the events do now
fire. However, they don't set the current record as we expect. AFAICT, this
problem exists in A2007 SP1 and SP2.

Hope I've understood the issue you are describing.

 

[brainlord]

We're all talking about the same thing

Yes Record Selectors are hidden.

Yes, this DID work from the 1st day I was using MSA2007. (Maybe that
was SP1) i.e all the events DID fire. (BTW the events still fire, just
on the wrong row.)

In fact I made this app in MSA *2007* BECAUSE of this new text bound
image control. This app has been working for a year now.

 

[brainlord]

my app is in public distribution. (not on a private net)

I have no control of what updates end-users install, esp with
Auto-updates.

I found this out when endusers reported problems

 

[brainlord]

All right I'm done with this. I have no time to wait for MS to pull
its head out.

I'm not going to build an example ACCDB, no one is paying me to.
Doesn't MS beta test this stuff?

I'm guessing this happened because MS was patching another security
hole for JPGs or something. Even if they hot-fix this now, I have
reason not to think they're just gonna pull this rug out from under me
again later.

Luckily this comes a conveinent point in our development cycle, we're
in Beta for the next build, and we're actually waiting for changes.

So we've recoded the form, placed transparent buttons over ALL the
image controls. And re-wrote 36 (yes 36) subs. (Thanks to consistant
control naming. that was mainly find-and-replace.)

Anyone who complains is just getting the new beta.

I don't mind having to code around built in limitations. But having MS
add new bugs to an App after I've sold it?! Please.

Are the *trying* to send me to OpenOffice?

 

[Tony Toews [MVP]]

I'm not going to build an example ACCDB, no one is paying me to.

Then tough. I'm not going to spend ten minutes or a half hour or more
creating a simplified case which it then turns out can't duplicate
your problem.

Doesn't MS beta test this stuff?

Yes, they do. But stuff happens.

So we've recoded the form, placed transparent buttons over ALL the
image controls. And re-wrote 36 (yes 36) subs. (Thanks to consistant
control naming. that was mainly find-and-replace.)

So you have a work around.

Are the *trying* to send me to OpenOffice?

So move to OpenOffice.

There's nothing there even close to Access.

You also didn't answer the question about if the record selector is
displayed on your form.

Tony

 

[Tony Toews [MVP]]

You also didn't answer the question about if the record selector is
displayed on your form.

Ah, actually you did in your reply to Allen. I saw this posting
before I saw that thread.

Tony

 

[David W. Fenton]

The image control in A2007 has a Control Source property, so this
is the first version you could make a continuous form and display
different images shown in each record.

That's not entirely true. I have been doing that since 1998 or so,
but do it by embedding an image in an OLE field and displaying that.
It's data so you get different images for each record:

http://dfenton.com/DFA/examples/SearchResults.gif

 

[David W. Fenton]

brainlord wrote in

I don't mind having to code around built in limitations. But
having MS add new bugs to an App after I've sold it?! Please.

Are the *trying* to send me to OpenOffice?

Calm down. Think about that for a moment. OpenOffice doesn't even
begin to compare to MS Office for programmability.

 

[David W. Fenton]

You also didn't answer the question about if the record selector
is displayed on your form.

Yes, he did -- it's not.