Access XP Runtime install fails/files not found - 2nd posting

[Robert Milligan]

(Second Posting - No response from 22-July submission)
For customers of my Access XP application product, they
are having difficulties installing Access 2002 XP Runtime
standalone, prior to installing my products:
1-On several PCs at different sites, running
ACCESSRT.MSI, yields: "Error 1311. Source file not
found:\D:\FILES\OFFICE1.CAB. Verify that the file exists
and that you can access it.". The files are present. Is
it necessary to stoop to writing DOS Path statements?
2-I cannot find documentation anywhere for the Access
Runtime installation. I am deploying Microsoft Office
Applications throughout the world and this information is
essential for all XP developers and their customers.
This is a Microsoft marketing issue, as it promotes sales
of Office XP's Professional edition.

 

[Robert Milligan]

Greg,

Thank you for your good suggestion. Actually, for ten
years I have been successfully deploying my Access
applications throughout the US and abroad to a half dozen
countries (not to boast). Some may be surprised that I
have thus far relied exclusively upon the Access
distribution tools. Naturally, I have considered many
times alternative products for distribution, but I have
somehow worked through all the glitches, and complement
my distributed product with ample Microsoft Access and
Office installation information to my customer base to
help them through the different Access platform and
compatibility issues.

Access has, it seems, been a step-child in the world of
Microsoft developers, as Microsoft documentation products
and develpment resources seems to focus on other
products, such as VB and C. Nonetheless, Access's long
and careful product development, beginning 15 years ago,
and its battle-proven shell have shown it to be a
powerful and extremely reliable production tool. The
business world has most benefitted from this product.
Microsoft Office teams ought to recognize its value as a
successful marketing tool for Office Professional, too.

So here we are now, with all the potential business value
and Microsoft is ...asleep. Or, are you?

 

[Greg Homyer]

Robert,

The statement, "...asleep. Or, are you? ", was meant for
(Microsoft). I'm very sorry for the misunderstanding.

Ditto. ...and I should have removed the vinegar from my last post regarding
the misunderstanding, or refrained from posting it in the first place.

--
Greg Homyer

Greg,

The statement, "...asleep. Or, are you? ", was meant for
(Microsoft). I'm very sorry for the misunderstanding.

Just to find closure on our topic:
- According to feedback from my customers, most don't
really read any documentation, and successfully install
directly from the Autoplay-Install on the CD-ROM. I added
a VB.EXE installer that provides information, then kicks
off the PDW installer. So, it isn't really all that bad
and takes only about two minutes for most. The extra
documentation I referred to is for those who ~might~ have
a problem, and for the IT support teams who want every
question answered before they bless the installation of
my software on their [user's] workstation.
- I will look forward to exploring SageKey products in
the future. I will countenance any feature that will
improve my product. It's just a matter of my resources
and what I can accomplish.
- Mike Groh, in the August Access VB SQL Advisor, writes
that, "I know of no commercially available application
written in Acess, although there are a few that use
the .MDB file format for their data." I can think of at
least one. Do you also have one? He also espouses
SageKey in a similar manner as you have done, and I am
sure it deserves all the praise.

Thank you very kindly for contributing your thoughts. I
would like to hear more about your product(s).

Rob