I am trying to develop a strategy for distributing Access97 run-time applications to remote users. Since the introduction of Windows2000, ME and XP a number of new version issues have arisen. For example:
Q162961: Run-time App Cannot Find System.mdw
(ie Computer does not have system.mdw file.
Q248112: Acess97 Run-time Incorrectly Uses Access 2000 Executable
(ie Computer attempts to open your run-time system with full Access 2000)
Q183143: Run-time App Changes Windows File Associations
(ie Computer does not know what to use to open database files any more – Full Access or run-time.
The point is, these FAQs all have fixes that are all very good on their own but I suspect that some of them are mutually exclusive. How is it possible to integrate them to cover all the different installation scenarios. My specific questions are:
Can anyone add to this thread with their own experience of trying to integrate these issues into a standard installation strategy?
I’m interested in tales of failure as well as success – it all helps.
Can anyone add other issues to this thread related to the Windows and Office versions of target machines?
There may be more issues that have a bearing.
Can anyone (THIS IS A BOLD ONE) demonstrate a successful approach to handling issues such as these?
This might be commercially sensitive - in this case a confident ‘Yes it is possible’ is better than nothing.
Bear in mind that this is about Run-time applications that could be distributed in their thousands over the internet, so there is no option to go to sites and implement machine specific fixes.
On a wider note:
Would anyone like a Tek-Tips Access97 Run-time development Forum?
With many thanks in advance to all of you out there trying to distribute Access97 Run-time Applications, jobo123
Q162961: Run-time App Cannot Find System.mdw
(ie Computer does not have system.mdw file.
Q248112: Acess97 Run-time Incorrectly Uses Access 2000 Executable
(ie Computer attempts to open your run-time system with full Access 2000)
Q183143: Run-time App Changes Windows File Associations
(ie Computer does not know what to use to open database files any more – Full Access or run-time.
The point is, these FAQs all have fixes that are all very good on their own but I suspect that some of them are mutually exclusive. How is it possible to integrate them to cover all the different installation scenarios. My specific questions are:
Can anyone add to this thread with their own experience of trying to integrate these issues into a standard installation strategy?
I’m interested in tales of failure as well as success – it all helps.
Can anyone add other issues to this thread related to the Windows and Office versions of target machines?
There may be more issues that have a bearing.
Can anyone (THIS IS A BOLD ONE) demonstrate a successful approach to handling issues such as these?
This might be commercially sensitive - in this case a confident ‘Yes it is possible’ is better than nothing.
Bear in mind that this is about Run-time applications that could be distributed in their thousands over the internet, so there is no option to go to sites and implement machine specific fixes.
On a wider note:
Would anyone like a Tek-Tips Access97 Run-time development Forum?
With many thanks in advance to all of you out there trying to distribute Access97 Run-time Applications, jobo123