Access 2003 Runtime and KB-945674

[amn]

After applying Service Pack 3, I had to apply this KB due error on
combobox with more than 31 fields on RowSource.

Hot Fix process installation completes successfully BUT nothing has
changed, that is, "MsAccess.exe" version still is 11.0.8166.0 (SP3)
instead of 11.0.8204.0 and error on combobox arises again.

"Add/Remove Programs" shows that KB-945674 has been installed.

I had another installation with "Access 2003 Retail" and everything
went fine.

Does anyone know an issue with this KB and Runtime version?

Best regards.

Angel.

 

[Jeanette Cunningham]

A few weeks ago I installed the runtime for A2003 on a client's computer.
There was a service pack type of file specifically for the runtime which I
also installed.
It has not needed any hotfix for combos, and I have not had any issues with
combos on that machine.



Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[amn]

A few weeks ago I installed the runtime for A2003 on a client's computer.
There was a service pack type of file specifically for the runtime which I
also installed.
It has not needed any hotfix for combos, and I have not had any issues with
combos on that machine.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

Hi Jeanette,

What I don't understand is the reason due a Service Pack is applied to
Access 2003 Runtime and Hot Fix only applies to "Retail" version. I
did not find any Service Pack/Fix specifically for Runtime version;
could you please provide some information about?

I have a combo with more than 31 fields and after SP3 I get the error
mentioned on KB-945674. I did a test removing the extra fields and
leaving only 31 fields and now everything was fine.

So, I need a way to apply the Fix to Runtime version or I will be
forced to rewrite the program to avoid having more than 31 fields.

Regards,

Angel.

 

[Jeanette Cunningham]

Apologies, when I checked further, I was mistaken about the version. I was
talking about 2007 runtime and not the A2003 runtime.
Better make a new post on this topic to see if someone else knows what to
do.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

A few weeks ago I installed the runtime for A2003 on a client's computer.
There was a service pack type of file specifically for the runtime which I
also installed.
It has not needed any hotfix for combos, and I have not had any issues
with
combos on that machine.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

Hi Jeanette,

What I don't understand is the reason due a Service Pack is applied to
Access 2003 Runtime and Hot Fix only applies to "Retail" version. I
did not find any Service Pack/Fix specifically for Runtime version;
could you please provide some information about?

I have a combo with more than 31 fields and after SP3 I get the error
mentioned on KB-945674. I did a test removing the extra fields and
leaving only 31 fields and now everything was fine.

So, I need a way to apply the Fix to Runtime version or I will be
forced to rewrite the program to avoid having more than 31 fields.

Regards,

Angel.

 

[Tom Wickerath]

Angel,

You might want to try some instructions written by Access MVP Sascha
Trowitzsch. You can find them here:
http://www.moss-soft.de/public/HowToCreateART11SP3.doc

That said, I really must ask why any combo box rowsource needs 31 fields!
The vast majority of combo box rowsources can be satisfied with 2-3 fields.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________

 

[amn]

Angel,

You might want to try some instructions written by Access MVP Sascha
Trowitzsch. You can find them here:http://www.moss-soft.de/public/HowToCreateART11SP3.doc

That said, I really must ask why any combo box rowsource needs 31 fields!
The vast majority of combo box rowsources can be satisfied with 2-3 fields.

Tom Wickerath
Microsoft Access MVPhttp://www.accessmvp.com/TWickerath/
__________________________________________

Tom,

You are right, 31 fields are too much. This program was created 9
years ago ( in my beginnings with Access) and you know ... if it works
don't touch it.

I have no problem to modify it but what I really would like to confirm
is that a "HotFix" only updates >>Retail<< versions; I could not find
any info that clarify this and it is very important to know.

Regards,

 

[Tony Toews [MVP]]

but what I really would like to confirm
is that a "HotFix" only updates >>Retail<< versions; I could not find
any info that clarify this and it is very important to know.

Do you have the Access runtime and the retail version of Access
installed on the same system or different systems. If the same system
then it very well may be that the hotfix patch process can't cope with
two on the same system.

I did use Sasha's process to create an ART with SP3 and some hotfixes
in it as well. Although IIRC the Microsoft Update wanted to update
the Access runtime anyhow.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[amn]

Do you have the Access runtime and the retail version of Access
installed on the same system or different systems.  If the same system
then it very well may be that the hotfix patch process can't cope with
two on the same system.

I did use Sasha's process to create an ART with SP3 and some hotfixes
in it as well.  Although IIRC the Microsoft Update wanted to update
the Access runtime anyhow.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
  updated seehttp://www.autofeupdater.com/
Granite Fleet Managerhttp://www.granitefleet.com/

Tony,

Customer workstation has installed "Access 97 Retail" and "Access 2003
Runtime".

"Access 97 Retail" is no longer used from 2 months ago that I upgraded
to "Access 2003 Runtime".

So, I made a test on a Virtual PC that ONLY has Windows XP SP3 (no
Office at all):
1. I installed Access 2003 Runtime using SageKey with success.
2. I installed Office SP2 with success.
3. I installed Office SP3 with success.
4. I installed KB-945674 BUT "MsAccess.exe" has not been updated.

I made another test on a Virtual PC with "Access 2003 Retail SP2":
1. I installed Office SP3 with success
2. I installed KB-945674 with success

So, it seems that "HotFix" does not update "Runtime" installations
(Customer workstation and mine using Virtual PC) and I have no idea
about other things to try.

Regards,

 

[Tony Toews [MVP]]

Customer workstation has installed "Access 97 Retail" and "Access 2003
Runtime".

"Access 97 Retail" is no longer used from 2 months ago that I upgraded
to "Access 2003 Runtime".

So, I made a test on a Virtual PC that ONLY has Windows XP SP3 (no
Office at all):
1. I installed Access 2003 Runtime using SageKey with success.
2. I installed Office SP2 with success.
3. I installed Office SP3 with success.
4. I installed KB-945674 BUT "MsAccess.exe" has not been updated.

I made another test on a Virtual PC with "Access 2003 Retail SP2":
1. I installed Office SP3 with success
2. I installed KB-945674 with success

So, it seems that "HotFix" does not update "Runtime" installations
(Customer workstation and mine using Virtual PC) and I have no idea
about other things to try.

However Sagekey is in the middle there. I have no idea as to the
details as to how Sagekey works. However they may install the
software in such a way that hotfixes don't install. You'll have to
talk to them.

I'd suggest trying a runtime without Sagekey and see what happens.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[amn]

However Sagekey is in the middle there.  I have no idea as to the
details as to how Sagekey works.  However they may install the
software in such a way that hotfixes don't install.  You'll have to
talk to them.

I'd suggest trying a runtime without Sagekey and see what happens.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
  updated seehttp://www.autofeupdater.com/
Granite Fleet Managerhttp://www.granitefleet.com/

Tony,

I already reported this on SageKey forum and a staff member told me
that anyone at SageKey is aware of this problem. Also they told me
that "Microsoft Access 2003 Runtime" is a different product that
"Microsoft Access 2003" and the KB info only mentions "Microsoft
Access 2003".

I can't imagine that Microsoft was not aware of this ... but who
knows !!!.

With this thread I was trying to find someone that applied this KB
with success in a "pure" Runtime installation (not Retail) but it
seems that I am the only one in this "galaxy".

I am in a hurry to solve this and by now, the faster way will be to
modify the app. Nevertheless, I will spend some time in other
workarounds as suggested by you, asap.

Thanks so much for your help.

Angel,

 

[Tony Toews [MVP]]

I already reported this on SageKey forum and a staff member told me
that anyone at SageKey is aware of this problem. Also they told me
that "Microsoft Access 2003 Runtime" is a different product that
"Microsoft Access 2003" and the KB info only mentions "Microsoft
Access 2003".

I can't imagine that Microsoft was not aware of this ... but who
knows !!!.

With this thread I was trying to find someone that applied this KB
with success in a "pure" Runtime installation (not Retail) but it
seems that I am the only one in this "galaxy".

I am in a hurry to solve this and by now, the faster way will be to
modify the app. Nevertheless, I will spend some time in other
workarounds as suggested by you, asap.

I'm not willing to spend the hour or two that it would take to setup
such an exact duplicate of your environment. By using products such
as Virtual PC or VMWare you can do this yourself. This is highly
recommended for basic testing of installs in any event.

Note that once you setup a clean guest operating system then only work
in a copy of it. So that whenever you want you can delete the copy,
make another one and continue testing.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[amn]

I'm not willing to spend the hour or two that it would take to setup
such an exact duplicate of your environment.  By using products such
as Virtual PC or VMWare you can do this yourself.  This is highly
recommended for basic testing of installs in any event.

Note that once you setup a clean guest operating system then only work
in a copy of it.  So that whenever you want you can delete the copy,
make another one and continue testing.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
  updated seehttp://www.autofeupdater.com/
Granite Fleet Managerhttp://www.granitefleet.com/

Tony,

I appreciate a lot your efforts to help me with this problem; this is
the current status:

.. The issue raised in a customer workstation with Access 2003 Runtime
installed. At the beginning I was totally confused because in another
customer workstation with Access 2003 Retail, everything was fine.
.. So, I used (as suggested by you) a Virtual PC environment to test
it. In a "Windows XP SP3" virtual environment with "no office at all"
I could test that Access 2003 Runtime fails and Access 2003 Retail
ends with success.
.. I was in touch with Sagekey that confirmed that they don't know this
problem in any customer.
.. Diving many hours in the web trying to get some light about, I was
able to find another case in a french forum but with no solution
published.
.. Although, I am able to modify the program and bypass the KB-945674
installation, I decided to find out the root of this problem; even
spending 200 Euros from my pocket. I am a developer and I can't sleep
well if I have no reason for an unsolved problem. So, I raised an
incident at Microsoft Spain.
.. Last Friday, I was in touch with a Microsoft Engineer and she was
able to see (through a remote access to my computer) the problem.
.. I sent to Microsoft all files involved (Sagekey distribution) so
they can reproduce the issue locally.
.. I will have another contact tomorrow, Monday, where I hope to get
news about.

I will keep you up to date.

Best regards,

Angel.

 

[amn]

Tony,

I appreciate a lot your efforts to help me with this problem; this is
the current status:

. The issue raised in a customer workstation with Access 2003 Runtime
installed. At the beginning I was totally confused because in another
customer workstation with Access 2003 Retail, everything was fine.
. So, I used (as suggested by you) a Virtual PC environment to test
it. In a "Windows XP SP3" virtual environment with "no office at all"
I could test that Access 2003 Runtime fails and Access 2003 Retail
ends with success.
. I was in touch with Sagekey that confirmed that they don't know this
problem in any customer.
. Diving many hours in the web trying to get some light about, I was
able to find another case in a french forum but with no solution
published.
. Although, I am able to modify the program and bypass the KB-945674
installation, I decided to find out the root of this problem; even
spending 200 Euros from my pocket. I am a developer and I can't sleep
well if I have no reason for an unsolved problem. So, I raised an
incident at Microsoft Spain.
. Last Friday, I was in touch with a Microsoft Engineer and she was
able to see (through a remote access to my computer) the problem.
. I sent to Microsoft all files involved (Sagekey distribution) so
they can reproduce the issue locally.
. I will have another contact tomorrow, Monday, where I hope to get
news about.

I will keep you up to date.

Best regards,

Angel.

Tony,

Yesterday I was in touch with Microsoft Support Engineer who confirmed
the issue by installing Runtime and applying hot fix, in its servers.
Nevertheless, Microsoft got it working fine by using the "standard"
Access 2003 installation wizard (not Sagekey) BUT using Runtime in
english.
That made me think about trying a different approach, so I decided to
create a new Sagekey package BUT using now Runtime in english.
Then, I did following:
1. create a Sagekey package using Runtime in english (and installing
it afterwards).
2. Apply SP3 in english.
3. Apply KB-945674

.... and now, everything was fine and "MsAccess.exe" has now
11.0.8204.0 version.

So, my final conclusion is that KB-945674 hotfix has a problem with
Access 2003 Runtime "in spanish".

I forwarded all of this to Microsoft Support Engineer and right now I
am waiting for news from Microsoft.

Best regards,

Angel.

 

[amn]

Tony,

Yesterday I was in touch with Microsoft Support Engineer who confirmed
the issue by installing Runtime and applying hot fix, in its servers.
Nevertheless, Microsoft got it working fine by using the "standard"
Access 2003 installation wizard (not Sagekey) BUT using Runtime in
english.
That made me think about trying a different approach, so I decided to
create a new Sagekey package BUT using now Runtime in english.
Then, I did following:
1. create a Sagekey package using Runtime in english (and installing
it afterwards).
2. Apply SP3 in english.
3. Apply KB-945674

... and now, everything was fine and "MsAccess.exe" has now
11.0.8204.0 version.

So, my final conclusion is that KB-945674 hotfix has a problem with
Access 2003 Runtime "in spanish".

I forwarded all of this to Microsoft Support Engineer and right now I
am waiting for news from Microsoft.

Best regards,

Angel.

Well, Microsoft Support has found out the clue to solve this.

It is absolutely mandatory to install "critical update" KB-943452
after SP3, but only for specific languages (main european apart of
english).

In case someone is on troubles with a post-service SP3 hotfix and
related with specified languages, please install KB-943452 and after
the hotfix again, selecting "Reinstall or Repair".

Best regards.

Angel.

 

[Tony Toews [MVP]]

Well, Microsoft Support has found out the clue to solve this.

It is absolutely mandatory to install "critical update" KB-943452
after SP3, but only for specific languages (main european apart of
english).

In case someone is on troubles with a post-service SP3 hotfix and
related with specified languages, please install KB-943452 and after
the hotfix again, selecting "Reinstall or Repair".

Wow! Thanks for posting your resolution. Not at all obvious. I'll
make my fellow MVPs aware of this solution.

Just curious. Did you end up having to pay for the support call?

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[amn]

Wow!  Thanks for posting your resolution.  Not at all obvious.  I'll
make my fellow MVPs aware of this solution.

Just curious.  Did you end up having to pay for the support call?

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
  updated seehttp://www.autofeupdater.com/
Granite Fleet Managerhttp://www.granitefleet.com/

Tony,

About payment, well, at first glance I will have to pay but case will
be sent to Customer Dept. and they will say the last word.

I will keep you up to date.

Regards,

Angel.