D
david
Any new OS or version of Access usually makes my database unhappy. Often
the cause is CommonDialog or another of the (to me) mysterious things
working in the background. Giving someone a copy to use on their equipment
is often a waste of time. As far as possible, I'd like to
past-and-future-proof, and "new-environment-proof", the database. This
includes changes in screen resolution. Dream on?
Microsoft's article ID 161286 seems to suggest that for some functions at
least, chunks of code can be downloaded that do comdlg**.***'s job. Perhaps
this is also true of other likely causes of malfunction? Article 180284,
about "Distributable Run-Time Applications", doesn't seem to address such
matters.
The database, created with Windows98 and Office Professional 97, currently
running under XP and Office Professional 97, is split. References list VBA,
8.0 Object Library, DAO 3.5 Object Library, and COMDLG32.OCX. But it still
complains that other things are missing: eg cmdlg98.chm, when some keyword
is highlighted and I press F1. CommonDialog seems only to be in some
shortish professionally-written subs to do with image management in the
"Forms end": "ctlCommonDialog.InitDir =" and "ctlCommonDialog.ShowOpen" and
"= ctlCommonDialog.FileTitle" (which don't work reliably anyway). There's
also ctlHelpFile, which has never caused trouble yet. The "Tables end" has
only Tables, and no References that I could find.
I'd be very grateful for comments - general or specific - based on your
experience in these matters.
David
the cause is CommonDialog or another of the (to me) mysterious things
working in the background. Giving someone a copy to use on their equipment
is often a waste of time. As far as possible, I'd like to
past-and-future-proof, and "new-environment-proof", the database. This
includes changes in screen resolution. Dream on?
Microsoft's article ID 161286 seems to suggest that for some functions at
least, chunks of code can be downloaded that do comdlg**.***'s job. Perhaps
this is also true of other likely causes of malfunction? Article 180284,
about "Distributable Run-Time Applications", doesn't seem to address such
matters.
The database, created with Windows98 and Office Professional 97, currently
running under XP and Office Professional 97, is split. References list VBA,
8.0 Object Library, DAO 3.5 Object Library, and COMDLG32.OCX. But it still
complains that other things are missing: eg cmdlg98.chm, when some keyword
is highlighted and I press F1. CommonDialog seems only to be in some
shortish professionally-written subs to do with image management in the
"Forms end": "ctlCommonDialog.InitDir =" and "ctlCommonDialog.ShowOpen" and
"= ctlCommonDialog.FileTitle" (which don't work reliably anyway). There's
also ctlHelpFile, which has never caused trouble yet. The "Tables end" has
only Tables, and no References that I could find.
I'd be very grateful for comments - general or specific - based on your
experience in these matters.
David