GetOpenFilename correct path workaround?

[Geoff_Strickler]

Version: 2004 Operating System: Mac OS X 10.5 (Leopard) Processor: Intel I've just encountered the problem described (in another thread by Bob Greenblatt) below:

If you want to get the file path as a string,
use application.getopenfilename. Be careful, however, as this will NOT
return the correct and full path, if the user navigates to the file by
flipping the disclosure triangles in the dialog. If, instead, they double
click on folders to open them, then the path is correct. Some sample code
would look like:
Xxx=application.getopenfilename
...."Text;"&xxx,destination.....

Is there a fix or workaround for getting the correct path even if the user navigates using the triangles instead of opening each folder?

 

[Bob Greenblatt]

Version: 2004 Operating System: Mac OS X 10.5 (Leopard) Processor: Intel I've
just encountered the problem described (in another thread by Bob Greenblatt)
below:

If you want to get the file path as a string,
use application.getopenfilename. Be careful, however, as this will NOT
return the correct and full path, if the user navigates to the file by
flipping the disclosure triangles in the dialog. If, instead, they double
click on folders to open them, then the path is correct. Some sample code
would look like:
Xxx=application.getopenfilename
..."Text;"&xxx,destination.....

Is there a fix or workaround for getting the correct path even if the user
navigates using the triangles instead of opening each folder?

NO! There is no fix. The ONLY work around is to have the user double click
the folder rather than use the disclosure triangle.

 

[Geoff_Strickler]

Thanks Bob. Not the answer I was hoping for, but at least I know how to answer questions if it comes up.