> Before opening a file I have to find out its name and location, because in
> some cases the user selects a shortcut file (*.lnk) instead of the data file
> itself.

> When I fire the Open statement with the *.lnk filename I don't get the
> target file opened but the shortcut only.

> Is there some kind of "indirect open" statement, solving the shortcut? Or is
> there an API to solve the shortcut, i.e. with the lnk filename as an
> argument and returning the target filename?

> Somewhere I found a format description of "The Windows Shortcut File Format
> as reverse-engineered by Jesse Hager" which I will use if there is no easier
> way.

> Paul
> please email me

> Before opening a file I have to find out its name and location, because in
> some cases the user selects a shortcut file (*.lnk) instead of the data
file
> itself.

> When I fire the Open statement with the *.lnk filename I don't get the
> target file opened but the shortcut only.

> Is there some kind of "indirect open" statement, solving the shortcut? Or
is
> there an API to solve the shortcut, i.e. with the lnk filename as an
> argument and returning the target filename?

> Somewhere I found a format description of "The Windows Shortcut File
Format
> as reverse-engineered by Jesse Hager" which I will use if there is no
easier
> way.