🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.cppbuilder.nativeapi
Article #10534

Re: trying to acces to a file by means of a link file

#10534
From: Damon Chandler (TeamB)
Date: Fri, 02 Apr 2004 01:15
16 lines
1451 bytes
Hi Frank,
   You can use the IShellLink COM interface to retrieve the 
path+filename of the file that the link refers to; see here for an 
example...

http://tinyurl.com/2taea

Good luck,
--
Damon (TeamB)


Frank Chisme wrote:
> where "fName" is "personal.ini.lnk".
> And my application doesn�t get to personal.ini content.
> �How can I access personal.ini file by means of personal.ini.lnk?
Technical Details
Message-ID: <406cbe4b$1@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!in.100proofnews.com!in.100proofnews.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail
References: <406c1fc2$1@newsgroups.borland.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII
X-Google-Thread: 10cc67,a53a58dfad4a9f1a
X-Google-Attributes: gid10cc67,public
X-Google-ArrivalTime: 2004-04-01 17:20:13 PST
Date: Thu, 01 Apr 2004 20:15:06 -0500
From: "Damon Chandler (TeamB)" <dmc27@cornell.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: borland.public.cppbuilder.nativeapi
Subject: Re: trying to acces to a file by means of a link file
References: <406c1fc2$1@newsgroups.borland.com>
In-Reply-To: <406c1fc2$1@newsgroups.borland.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
NNTP-Posting-Host: 24.58.5.101
Message-ID: <406cbe4b$1@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1080868427 24.58.5.101 (1 Apr 2004 17:13:47 -0800)
Lines: 16
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!in.100proofnews.com!in.100proofnews.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail