Maybe I should null out the association. I'll put that on the 'to try' list.

Same issue for me, same fix.

Guy,

So you've fixed it ? How, by disassociating .veg with Vegas?

I tried to reproduce your error and I could not do it.

I created a new VP 12 project. I added a nested project created in VP 12. From the timeline, I was then able to edit it in a new instance of VP 12.

Then I created a new project in VP 12 and added a nested project created in VP 11. From the timeline, I was then able to edit it in a new instance of VP 11.

What I could not do was add a VP 12 nested project to a VP 11 project. I just kept getting the red circle with a slash through it, but no error message.

So when you try to set the default file/open parameters, it doesn't work for you? That is strange.

I can associate V12 (or V10 for that matter) with the .veg so that double clicking on a project or shortcut opens the .veg in the correct Vegas program. It does work

I haven't tried to add a V10 or V11 project to a V12 timeline.

What doesn't work is:-
I add newly created V12 project into a newly created V12 project's timeline and I get the error in my OP when I try to edit the nested project from the timeline

I had found a switch in Vegas which gave me more information (but I can't remember now where I found it) but it told me that it was trying to open the nested V12 project with V11 - that's why I removed V11.

Windows file associations are working; editing a nested V12 project from a V12 project's timeline isn't working even though the windows file association is .veg = V12

I see the same behavior on my system -- all .veg files correctly open with Vegas 12 on my system, unless I try to open a nested .veg. Vegas then attempts to open the nest with Vegas 8. So far I haven't any luck getting it to work correctly and open with Vegas 12.

It seems like it's some sort of registry entry causing the issue.

Jim

So this does not work for you?

Use Windows Explorder to locate a *.veg file (any file will do).
Right-click the file.
Open With
Choose Default Program
Select Vegas 12.

As you may know, this sets the "open with" default for all *.veg files to open with Vegas 12.

Then try the nested file exercise. In theory, you should be able to edit it from the timeline with a second instance of Vegas 12.

Note that you will get error messages in the parent project if the media in the nested project has moved from the original location, but that is separate from the above issue.

I'm stumped if it doesn't work : (

Regards,

Kimberly

As for me -- Vegas 12 does open when I just double click on a veg from Windows. It's that while Vegas is open and I choose to edit a nested veg that the nested veg opens with Vegas 8. So, it's not Windows doing it -- it's something Vegas is doing...

This problem was solved (per a previous post by mbarton) by changing a registry setting:
Regedit
Find: HKCUsoftwareclasses.veg REG_SZ vegas110
Change to: HKCUsoftwareclasses.veg REG_SZ vegas120

I needed to find REG_SZ vegas80, but other than that, it worked! Thanks much :-)

Jim

dcrandall - you are a star, for re-posting that

and mbarton is a hero for sharing that

Once I'd deciphered what/where/how to change that, it worked as it should.

Thanks again :)