Re: Vulnerability in Microsoft Jet Database Engine Could Allow Rem

Are the joined tables in your query remote tables (Sql Server, Oracle, ...)
or are they tables stored in the Jet database? It sounds like your query
needed to be recompiled after installing the service pack. If the query goes
to remote data, has anything changed on the remote server or DSN, such as a
server upgrade, table schema change, etc? I don't know what caused the query
to need to be recompiled (if that was the case) but something like that could
trigger it.

Also, on a test machine you might try compacting the database after
upgrading to XP SP3 and see if the query works after the compact.

Lastly, in design mode after applying SP3, what appears to be corrupt?

Thanks,
-Curtis

"Greg" wrote:

Sorry I did not provide enough details, but since I posted we have come with
a solution, but I am still confused as to why this has happened in the first
place.

Anyway, the database I am referring to was started in MS Access 97, but has
grown over the years and is now developed in MS Access XP/2002. All of our
customers who stopped working were running Windows XP Pro. Initially, we had
to have all of our customers do a System Restore to the previous day and turn
off Automatic updates as a short term fix to get our customers up and
running, since we had no idea why our software worked one day just fine. I
really am not comfortable with making our customers have to do this. But
after the service packs were applied, either Windows XP Pro/Home Service Pack
3 and/or MS08-028. Both of these rendered our software broken in just a
single form (and of course it was the most important form: Order Entry - and
Job Ticket creation).

Anyway, it turns out this service pack prevented one out of several hundred
queries broken. The error message said something about not finding a database
to some degree. The query mearly returns a recordset with two tables joined.
The solution was to delete the query from the database and then I completely
created a brand new one and made aboslutely no changes. Actually, I copied
the SQL from the original query into the new query. This had to be done on a
machine that did not have the service packs installed.

Then, when we put the application back on the Service Pack 3 computer it now
runs fine with no errors.

What concerns me though is that the query functions and can be viewed in
design view just fine prior to the service pack, but appears currupt after
the service pack.

Why would a service pack, such as the ones I'm referring to cause a query to
stop working, even though it runs fine and can be viewed in design view prior
to the service pack update?

Anyway, we are back in business now, after a whole day of lost productivity
and a lot of angry customers. But, I would like to understand why this
happened at all and what is it the service packs are doing that would make a
perfectly good query useless afterwards.

Any light that can be shed on the Service Pack issue would be helpful. I
just want to understand what is going on more than anything at this point so
I can understand why one of our queries would become broken after a service
pack update so that I can be pro-active for our customers in the future.

Thanks,
Greg

"david" wrote:

Are you sure it is MS08-028 causing the problem,
rather than -026?

Is that an Access form? Or a VB form? Word? Excel?

You've made no changes in the last 10 years? That means you
are using Access 97/ Jet 3.51? Or do you mean that you only
updated to new versions of Access? Which version of what
software are you using?

(david)

"Greg" <AccessVBAnet@xxxxxxxxxxxxxxxxx> wrote in message
news:03B7AAF8-0F2E-420C-ABE1-54705C0D181E@xxxxxxxxxxxxxxxx
It appears Microsoft released a service pack update last night that
includes
the following as a part of the service pack:

MS08-028
Severity Level: Important
Vulnerability in Microsoft Jet Database Engine Could Allow Remote Code
Execution (950749)

It appears that after this service pack was applied at many of our
customer
sites (who apparently have automatic updates turned on). that all of our
customers can no longer get into one of our primary forms, our Order Entry
form.

Because we have made absolutely not changes to our software we have
concluded this update is the source of the problem and have in fact proved
it. We had one of our customers do a restore proint, that removed the
update
and our product works fine now, which has been in use for over 10 years
now.

Anyway, has anyone heard about problems arising because of this update and
if so, what are some of the solutions to allow our MS Access product to
work
with the service pack applied?

Thansk
Greg



.