Windows had .MYO extention linked to c:\myob14\myob.exe.
Updating to myob16, I cannot link .MYO to c:\myob16\myob.exe.

It seems to remember myob.exe and therefore already knows the link. It
doesn't change to c:\myob16.

If I copy c:\myob16\myob.exe to c:\myob16\mmmm.exe and link .MYO to that, it
works.

How can I include the folder name in the linked executable?
Doug

"Doug" <(E-Mail Removed)> wrote in message
news:51892656-DB34-4E8B-A533-(E-Mail Removed)...
> Windows had .MYO extention linked to c:\myob14\myob.exe.
> Updating to myob16, I cannot link .MYO to c:\myob16\myob.exe.
>
> It seems to remember myob.exe and therefore already knows the link. It
> doesn't change to c:\myob16.
>
> If I copy c:\myob16\myob.exe to c:\myob16\mmmm.exe and link .MYO to that,
it
> works.
>
> How can I include the folder name in the linked executable?
> Doug

I suspect your question is already answered on the MYOB FAQ
page. If not then the MYOB helpdesk will be able to tell you
straight away, since their upgrade program should have set the
correct association.

Doug <(E-Mail Removed)> wrote on Sun, 4 Mar 2007:

>Windows had .MYO extention linked to c:\myob14\myob.exe.
>Updating to myob16, I cannot link .MYO to c:\myob16\myob.exe.
>
>It seems to remember myob.exe and therefore already knows the link. It
>doesn't change to c:\myob16.
>
>If I copy c:\myob16\myob.exe to c:\myob16\mmmm.exe and link .MYO to that, it
>works.
>
>How can I include the folder name in the linked executable?

I don't quite get this, Doug. . . when you double-click on a .MYO file,
if Windows cannot find the .exe in \myob14, it should ask you which
program you want to use to open the file. Then it offers you a window
listing selected programs; if the one you want isn't there, you click
the Browse button and navigate to it and Windows will make the new file
association.

What happens when you double-click on a file, or use a shortcut to one?
Could it be that you still have MYOB 14 installed?

--
Nightowl

MYOB14, 15 and 16 are all installed.
The problem seems to be within Windows, not MYOB as, even if I change the
link and point to c:\myob16\myob.exe, clicking on a .MYO file opens myob14's
myob.exe, even though I specifically linked it to myob16.
I have worked around the problem by changing the two older myob.exe files to
myob14.exe and myob15.exe.
--
Doug


"Nightowl" wrote:

> Doug <(E-Mail Removed)> wrote on Sun, 4 Mar 2007:
>
> >Windows had .MYO extention linked to c:\myob14\myob.exe.
> >Updating to myob16, I cannot link .MYO to c:\myob16\myob.exe.
> >
> >It seems to remember myob.exe and therefore already knows the link. It
> >doesn't change to c:\myob16.
> >
> >If I copy c:\myob16\myob.exe to c:\myob16\mmmm.exe and link .MYO to that, it
> >works.
> >
> >How can I include the folder name in the linked executable?
>
> I don't quite get this, Doug. . . when you double-click on a .MYO file,
> if Windows cannot find the .exe in \myob14, it should ask you which
> program you want to use to open the file. Then it offers you a window
> listing selected programs; if the one you want isn't there, you click
> the Browse button and navigate to it and Windows will make the new file
> association.
>
> What happens when you double-click on a file, or use a shortcut to one?
> Could it be that you still have MYOB 14 installed?
>
> --
> Nightowl
>

Doug <(E-Mail Removed)> wrote on Mon, 5 Mar 2007:

>MYOB14, 15 and 16 are all installed.
>The problem seems to be within Windows, not MYOB as, even if I change the
>link and point to c:\myob16\myob.exe, clicking on a .MYO file opens myob14's
>myob.exe, even though I specifically linked it to myob16.
>I have worked around the problem by changing the two older myob.exe files to
>myob14.exe and myob15.exe.

That's a good solution, Doug.

I was going to suggest you add c:\myob16 to your system Path to see if
that fixed it. but your answer is better :-)

--
Nightowl

That is the problem, Nightowl. I changed the file type association to
inlcude the path c:\myob16, but double-clicking the .MYO file still started
the MYOB.EXE in C:\MYOB14. It would appear that, either windows "remembers"
the path from the original association, and, if the new executable is the
same name, doesn't change the path.

The problem has been worked around by changing all the "wrong" myob.exe
program names.
--
Doug


"Nightowl" wrote:

> Doug <(E-Mail Removed)> wrote on Mon, 5 Mar 2007:
>
> >MYOB14, 15 and 16 are all installed.
> >The problem seems to be within Windows, not MYOB as, even if I change the
> >link and point to c:\myob16\myob.exe, clicking on a .MYO file opens myob14's
> >myob.exe, even though I specifically linked it to myob16.
> >I have worked around the problem by changing the two older myob.exe files to
> >myob14.exe and myob15.exe.
>
> That's a good solution, Doug.
>
> I was going to suggest you add c:\myob16 to your system Path to see if
> that fixed it. but your answer is better :-)
>
> --
> Nightowl
>

Hi Doug

I meant the system path -- the environment variable (right-click My
Computer, choose Properties, Advanced tab, Environment Variables
button). Another way might be to delete that file type altogether,
reboot and then add it again, specifying c:\myob16. It might be there is
some persistent setting in the Registry that is overriding whatever you
put in the file associations dialog, but I think your solution is neat.

Doug <(E-Mail Removed)> wrote on Wed, 7 Mar 2007:

>That is the problem, Nightowl. I changed the file type association to
>inlcude the path c:\myob16, but double-clicking the .MYO file still started
>the MYOB.EXE in C:\MYOB14. It would appear that, either windows "remembers"
>the path from the original association, and, if the new executable is the
>same name, doesn't change the path.
>
>The problem has been worked around by changing all the "wrong" myob.exe
>program names.

>"Nightowl" wrote:
>
>> Doug <(E-Mail Removed)> wrote on Mon, 5 Mar 2007:
>>
>> >MYOB14, 15 and 16 are all installed.
>> >The problem seems to be within Windows, not MYOB as, even if I change the
>> >link and point to c:\myob16\myob.exe, clicking on a .MYO file opens myob14's
>> >myob.exe, even though I specifically linked it to myob16.
>> >I have worked around the problem by changing the two older myob.exe files to
>> >myob14.exe and myob15.exe.
>>
>> That's a good solution, Doug.
>>
>> I was going to suggest you add c:\myob16 to your system Path to see if
>> that fixed it. but your answer is better :-)
>>
>> --
>> Nightowl
>>

--
Nightowl