![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
"Albert D. Kallal" <PleaseNOOOsPAMmkallal (AT) msn (DOT) com> wrote in news:q3CVm.80878$W77.22569 (AT) newsfe11 (DOT) iad: Rich is on the right track. You can use: Dim f As FileDialog I had originally thought this required a reference to the Office library, but I see that FileDialog is a member of the Access.Application object, so it won't require it. I note that this was not the case in Access 2000 (I don't have A2002 to see if it was introduced there). I do see that it's still in A2007. However, given the experience with the FileSearch object (introduced in Office 95/97, and removed from Office 2007), I worry about depending on it always being there. Using the Windows API is going to be future-proof, as opposed to using a wrapper around it provided by the Access application, which could come and go with different versions. |
#12
| |||
| |||
|
|
Would you be kind enough to let me have a copy of the functions. The ones I use were written by Ken Gatz over 12 years ago |
#13
| |||
| |||
|
|
"Phil" <phil (AT) stantonfamily (DOT) co.uk> wrote in news:goednXSUyajAELXWnZ2dnUVZ8kWdnZ2d (AT) brightview (DOT) co.uk: Would you be kind enough to let me have a copy of the functions. The ones I use were written by Ken Gatz over 12 years ago In my apps I'm using the ADH97 versions. An earlier version of that is what's on the Access Web (http://mvps.org/access/api/api0001.htm). It's written against the Windows API -- it's not going to be broken in future versions of Windows because MS doesn't break its legacy APIs. Remember, DOS apps compiled in 1982 or so still run on current versions of Windows, and I don't expect that the Windows API will be omitted from whatever replaces Windows some day. That said, there very well may snazzier functionality in newer APIs, or in using the wrapper object in Access, but I'd rather stick with something that works and will continue to work as long as Windows exists. |
![]() |
| Thread Tools | |
| Display Modes | |
| |