Hi.

I am trying to package Access97 which should be installed on the sysetm already having Office 2003. When I am capturing Access 97 on a machine already having 2003, I given the installation directory as C:\Program Files\Microsoft Office\Access97. When I am trying to install packaged Access 97, its throwing Internal Error 2705. Directory checked the log file, saying Error 2705: Invalid table: Directory; Could not be linked as tree. Please help me out to solve this issue.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I am trying to package Access97 which should be installed on the sysetm already having Office 2003

1) LOL

When I am trying to install packaged Access 97, its throwing Internal Error 2705. Directory checked the log file, saying Error 2705: Invalid table: Directory; Could not be linked as tree.

2) Ever heard of validation? No? Thought not.
Answered 09/15/2010 by: dummypack
Senior Yellow Belt

Please log in to comment
0
Hi,

Did package validation giving ICE03 problem with parent directory. Checked all the entries in Directory table all are looking fine.
Answered 09/15/2010 by: ravi223966
Senior Yellow Belt

Please log in to comment
0
If the validation fails, then whether or not it looks "fine" is irrelevant, since it clearly isn't "fine".

Learn what the MSI tables are, how they interact and so on, THEN start packaging.

EDIT:
Which cheap-skate decided not to spring for Office Professional (to get Access 2003) but to try and shoe-horn in Access 97? And PLEASE don't give us the compatibility hoo-ha because I have dealt with more MDBs and MDEs than you can shake a stick at and I have yet to come across one which ran in 97 but not in 2003.
Answered 09/15/2010 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

If the validation fails, then whether or not it looks "fine" is irrelevant, since it clearly isn't "fine".

Learn what the MSI tables are, how they interact and so on, THEN start packaging.

EDIT:
Which cheap-skate decided not to spring for Office Professional (to get Access 2003) but to try and shoe-horn in Access 97?  And PLEASE don't give us the compatibility hoo-ha because I have dealt with more MDBs and MDEs than you can shake a stick at and I have yet to come across one which ran in 97 but not in 2003.


I've seen this scenario several times, often because somebody wrote a home grown access app that a later version breaks.

good point about the MSI tables. I am almost ashamed to say that I packaged for at least a year without even knowing that windows installer is a relational database. It was only when I had to step outside of Wise to do my job that I got to know the database tables fairly well.
Answered 09/15/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
somebody wrote a home grown access app that a later version breaksCheap-skate call again, then! Too cheap to engage a proper developer.
Answered 09/15/2010 by: VBScab
Red Belt

Please log in to comment
0
exactly. the real problems come when the "Access Expert" writes something that becomes popular or "business critical" and folks don't want to give it up. Big headaches getting upgrades done.
Answered 09/15/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity