Hello,

I'm about to deploy my first A2002 application. There were many problems
(bugs) as to A97 ODE and installation process on machines with different
versions of Access. Is there a list of bugs and other issues for A2002 PDW
as to co-existence with different versions of MS Access (MS Office) on the
same machine? I desperatelly need that my application will install and run
without any problem.

TIA

Vlado

On Thu, 24 May 2007 10:51:21 +0200, Vladimír Cvajniga <(E-Mail Removed)> wrote:

>Hello,
>
>I'm about to deploy my first A2002 application. There were many problems
>(bugs) as to A97 ODE and installation process on machines with different
>versions of Access. Is there a list of bugs and other issues for A2002 PDW
>as to co-existence with different versions of MS Access (MS Office) on the
>same machine? I desperatelly need that my application will install and run
>without any problem.

You'll have no end of troubles if you use the PDW to deploy the runtime. Most professional developers use the Sagekey
scripts (www.sagekey.com) to deploy their runtime apps with the ART. If you "desperately" need your app to run smoothly
and co-exist with other versions of Access, then do yourself a favor and invest in the Sagekey scripts.

BTW, these aren't "bugs" ... look up the definition online to see why.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

Thanx for your respond.

I'd appreciate if Microsoft would provide same quality as Sagekey. We pay
for MS products but we miss quality. Why do we have to pay twice?

Vlado

P.S. If there any problem with installation/run, to me it always be a bug.
:-/ MS call them "issues" or "problems" but, in fact, they're bugs...

"Scott McDaniel" <scott@NoSpam_Infotrakker.com> píse v diskusním príspevku
news:(E-Mail Removed)...
> On Thu, 24 May 2007 10:51:21 +0200, Vladimír Cvajniga <(E-Mail Removed)>
> wrote:
>
>>Hello,
>>
>>I'm about to deploy my first A2002 application. There were many problems
>>(bugs) as to A97 ODE and installation process on machines with different
>>versions of Access. Is there a list of bugs and other issues for A2002 PDW
>>as to co-existence with different versions of MS Access (MS Office) on the
>>same machine? I desperatelly need that my application will install and run
>>without any problem.
>
> You'll have no end of troubles if you use the PDW to deploy the runtime.
> Most professional developers use the Sagekey
> scripts (www.sagekey.com) to deploy their runtime apps with the ART. If
> you "desperately" need your app to run smoothly
> and co-exist with other versions of Access, then do yourself a favor and
> invest in the Sagekey scripts.
>
> BTW, these aren't "bugs" ... look up the definition online to see why.
>
> Scott McDaniel
> scott@takemeout_infotrakker.com
> www.infotrakker.com

On Thu, 24 May 2007 14:05:20 +0200, Vladimír Cvajniga <(E-Mail Removed)> wrote:

>Thanx for your respond.
>
>I'd appreciate if Microsoft would provide same quality as Sagekey. We pay
>for MS products but we miss quality. Why do we have to pay twice?

That's sort of like saying "I wish Internet Explorer would wash my car for me each week". Be nice, but it's not a
feature of IE. Overall the quality of MS products are pretty good, especially considering the userbase they must support
(which is, what, 90+% of the computer users out there?).

You don't have to pay twice; you can work your way through the 100's (if not 1000's) of registry keys that Access
writes/creates when it installs/launches, and build your own version of Sagekey ... or you can buy the scripts from
Sagekey and save yourself some time. It's up to you ... not MS.

>Vlado
>
>P.S. If there any problem with installation/run, to me it always be a bug.
>:-/ MS call them "issues" or "problems" but, in fact, they're bugs...

A "bug" is when an advertized, supported function doesn't work properly. MS has provided pretty clear instructions
regarding installing different versions of Access side-by-side, and if you follow those instructions you'll end up with
a decent installation, although you'll likely still run into the issue where Access "registers" itself as the progarm
associated with the .mde/.mdb extensions whenever it runs, so that the next time your enduser fires up the database
they're working on, they'll use the ART (unless they've configured their machine to explicitly call the correct version
of Access, or they're launching Access first and then opening the db).

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

"MS has provided pretty clear instructions
regarding installing different versions of Access side-by-side"

I've found only this one: http://support.microsoft.com/kb/241141.

Poor information for our end users who may not know too much about how to
handle various versions of Access. I hope, according to your previous
answer, that everything goes well during installation of A2002 app on end
users' machines. I hope there will be no problems similar to A97 <=> A2000
co-existence. In ODE97 I had to create 2 different installation sets. Is
this not necessary in A2002? Does A2002 runtime perform well on a machine
with:
A97
or
A2000
or
A2003
or
A2007
or
combinations of the above?

If there are some "issues", pls, let me know ASAP.

TIA

Vlado

"Scott McDaniel" <scott@NoSpam_Infotrakker.com> píse v diskusním príspevku
news:(E-Mail Removed)...
> On Thu, 24 May 2007 14:05:20 +0200, Vladimír Cvajniga <(E-Mail Removed)>
> wrote:
>
>>Thanx for your respond.
>>
>>I'd appreciate if Microsoft would provide same quality as Sagekey. We pay
>>for MS products but we miss quality. Why do we have to pay twice?
>
> That's sort of like saying "I wish Internet Explorer would wash my car for
> me each week". Be nice, but it's not a
> feature of IE. Overall the quality of MS products are pretty good,
> especially considering the userbase they must support
> (which is, what, 90+% of the computer users out there?).
>
> You don't have to pay twice; you can work your way through the 100's (if
> not 1000's) of registry keys that Access
> writes/creates when it installs/launches, and build your own version of
> Sagekey ... or you can buy the scripts from
> Sagekey and save yourself some time. It's up to you ... not MS.
>
>>Vlado
>>
>>P.S. If there any problem with installation/run, to me it always be a bug.
>>:-/ MS call them "issues" or "problems" but, in fact, they're bugs...
>
> A "bug" is when an advertized, supported function doesn't work properly.
> MS has provided pretty clear instructions
> regarding installing different versions of Access side-by-side, and if you
> follow those instructions you'll end up with
> a decent installation, although you'll likely still run into the issue
> where Access "registers" itself as the progarm
> associated with the .mde/.mdb extensions whenever it runs, so that the
> next time your enduser fires up the database
> they're working on, they'll use the ART (unless they've configured their
> machine to explicitly call the correct version
> of Access, or they're launching Access first and then opening the db).
>
> Scott McDaniel
> scott@takemeout_infotrakker.com
> www.infotrakker.com

OTOH, have you ever bought a new car without wheels? Just with instructions
how to mount wheels? I don't think so. Microsoft sells "cars without wheels"
(Access with "issues", ie. bugs) and provides "information how to mount
wheels" (MSDN, Knoledge Base, etc.).
In other words, un-professional job. In many cases it is very difficult to
get the right information at the right time or there is no information
available ("car without wheels" only). :-/

MS should slow down they run and carry about their products. IMO, at the
moment they just run for money.

Vlado

Vlado
"Scott McDaniel" <scott@NoSpam_Infotrakker.com> píse v diskusním príspevku
news:(E-Mail Removed)...
> On Thu, 24 May 2007 14:05:20 +0200, Vladimír Cvajniga <(E-Mail Removed)>
> wrote:
>
>>Thanx for your respond.
>>
>>I'd appreciate if Microsoft would provide same quality as Sagekey. We pay
>>for MS products but we miss quality. Why do we have to pay twice?
>
> That's sort of like saying "I wish Internet Explorer would wash my car for
> me each week". Be nice, but it's not a
> feature of IE. Overall the quality of MS products are pretty good,
> especially considering the userbase they must support
> (which is, what, 90+% of the computer users out there?).
>
> You don't have to pay twice; you can work your way through the 100's (if
> not 1000's) of registry keys that Access
> writes/creates when it installs/launches, and build your own version of
> Sagekey ... or you can buy the scripts from
> Sagekey and save yourself some time. It's up to you ... not MS.
>
>>Vlado
>>
>>P.S. If there any problem with installation/run, to me it always be a bug.
>>:-/ MS call them "issues" or "problems" but, in fact, they're bugs...
>
> A "bug" is when an advertized, supported function doesn't work properly.
> MS has provided pretty clear instructions
> regarding installing different versions of Access side-by-side, and if you
> follow those instructions you'll end up with
> a decent installation, although you'll likely still run into the issue
> where Access "registers" itself as the progarm
> associated with the .mde/.mdb extensions whenever it runs, so that the
> next time your enduser fires up the database
> they're working on, they'll use the ART (unless they've configured their
> machine to explicitly call the correct version
> of Access, or they're launching Access first and then opening the db).
>
> Scott McDaniel
> scott@takemeout_infotrakker.com
> www.infotrakker.com

they are bugs ****nut

Microsoft sells buggy ass software

and they're too busy selling Xbox and Live Earth and all this other crap

I mean get real Microsoft


STOP SELLING BUGGY ASS SOFTWARE!



"Scott McDaniel" <scott@NoSpam_Infotrakker.com> wrote in message
news:(E-Mail Removed)...
> On Thu, 24 May 2007 10:51:21 +0200, Vladimír Cvajniga <(E-Mail Removed)>
> wrote:
>
>>Hello,
>>
>>I'm about to deploy my first A2002 application. There were many problems
>>(bugs) as to A97 ODE and installation process on machines with different
>>versions of Access. Is there a list of bugs and other issues for A2002 PDW
>>as to co-existence with different versions of MS Access (MS Office) on the
>>same machine? I desperatelly need that my application will install and run
>>without any problem.
>
> You'll have no end of troubles if you use the PDW to deploy the runtime.
> Most professional developers use the Sagekey
> scripts (www.sagekey.com) to deploy their runtime apps with the ART. If
> you "desperately" need your app to run smoothly
> and co-exist with other versions of Access, then do yourself a favor and
> invest in the Sagekey scripts.
>
> BTW, these aren't "bugs" ... look up the definition online to see why.
>
> Scott McDaniel
> scott@takemeout_infotrakker.com
> www.infotrakker.com

Vlad

I applaud your courage



"Vladimír Cvajniga" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanx for your respond.
>
> I'd appreciate if Microsoft would provide same quality as Sagekey. We pay
> for MS products but we miss quality. Why do we have to pay twice?
>
> Vlado
>
> P.S. If there any problem with installation/run, to me it always be a bug.
> :-/ MS call them "issues" or "problems" but, in fact, they're bugs...
>
> "Scott McDaniel" <scott@NoSpam_Infotrakker.com> píse v diskusním príspevku
> news:(E-Mail Removed)...
>> On Thu, 24 May 2007 10:51:21 +0200, Vladimír Cvajniga <(E-Mail Removed)>
>> wrote:
>>
>>>Hello,
>>>
>>>I'm about to deploy my first A2002 application. There were many problems
>>>(bugs) as to A97 ODE and installation process on machines with different
>>>versions of Access. Is there a list of bugs and other issues for A2002
>>>PDW
>>>as to co-existence with different versions of MS Access (MS Office) on
>>>the
>>>same machine? I desperatelly need that my application will install and
>>>run
>>>without any problem.
>>
>> You'll have no end of troubles if you use the PDW to deploy the runtime.
>> Most professional developers use the Sagekey
>> scripts (www.sagekey.com) to deploy their runtime apps with the ART. If
>> you "desperately" need your app to run smoothly
>> and co-exist with other versions of Access, then do yourself a favor and
>> invest in the Sagekey scripts.
>>
>> BTW, these aren't "bugs" ... look up the definition online to see why.
>>
>> Scott McDaniel
>> scott@takemeout_infotrakker.com
>> www.infotrakker.com
>

Scott

I don't believe that it's possible to install a copy of the Access Runtime
that will get upgraded using Microsoft Update-- like it shoudl.

Stop making excuses for Microsoft, kid





"Scott McDaniel" <scott@NoSpam_Infotrakker.com> wrote in message
news:(E-Mail Removed)...
> On Thu, 24 May 2007 14:05:20 +0200, Vladimír Cvajniga <(E-Mail Removed)>
> wrote:
>
>>Thanx for your respond.
>>
>>I'd appreciate if Microsoft would provide same quality as Sagekey. We pay
>>for MS products but we miss quality. Why do we have to pay twice?
>
> That's sort of like saying "I wish Internet Explorer would wash my car for
> me each week". Be nice, but it's not a
> feature of IE. Overall the quality of MS products are pretty good,
> especially considering the userbase they must support
> (which is, what, 90+% of the computer users out there?).
>
> You don't have to pay twice; you can work your way through the 100's (if
> not 1000's) of registry keys that Access
> writes/creates when it installs/launches, and build your own version of
> Sagekey ... or you can buy the scripts from
> Sagekey and save yourself some time. It's up to you ... not MS.
>
>>Vlado
>>
>>P.S. If there any problem with installation/run, to me it always be a bug.
>>:-/ MS call them "issues" or "problems" but, in fact, they're bugs...
>
> A "bug" is when an advertized, supported function doesn't work properly.
> MS has provided pretty clear instructions
> regarding installing different versions of Access side-by-side, and if you
> follow those instructions you'll end up with
> a decent installation, although you'll likely still run into the issue
> where Access "registers" itself as the progarm
> associated with the .mde/.mdb extensions whenever it runs, so that the
> next time your enduser fires up the database
> they're working on, they'll use the ART (unless they've configured their
> machine to explicitly call the correct version
> of Access, or they're launching Access first and then opening the db).
>
> Scott McDaniel
> scott@takemeout_infotrakker.com
> www.infotrakker.com