Rick,
When you make an association, the package manager is essentially looking
for the .we file to include. In this case, you would want to include
Notepad.we.
HTH,
Steve
On 4/22/2011 6:55 AM, RicksPlace wrote:
Hi: I specified NotePad in the Associate field when I created my wepm
file. Evidently that was not good enough so I am wondering...
Do I have to specify the entire file path, just NotePad.exe if the
file is registered in the Registry or what others have done here.
Also, I went into Package Manager to see what the Association was but
couldn't get tab or cursor to get to the AssociatWith box. I could get
there with the WE Mouse and click it and hear an Empty EditBox. Is
this field disabled or just removed from the tab set? I wonder if I
can just enter the correct file into this field by mouse clicking it
and entering a correct file name or full path or something.
Or, do I have to ReBuild the entire wepm file from scratch?
I had noticed, and I think another fellow noticed, the NotePad2011 app
was not installed as a running app associated with NotePad when I used
App Get. I am thinking this is because the Association did not take
when I built the wepm file. I do not recall getting any error or
warning message from the Package Manager when I built the wepm file
but that was the first time I used it so may have missed it if it was
not spoken or popped up in a messagebox.
Can you tell me if I can just update the wepm file to add the NotePad
association and,
Do I need a full file path in the Association field even if NotePad is
usually in folks registry?
Rick USA
--
--
Stephen Clower
Product support specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
