I installed the latest version and got a "Encountered improper argument" error and locked up. I saved right before it hit. I do believe it's text boxs overlapping pictures thats causing the problem. I can't get the error if I intentionally overlap. Mine popped when I went to up load. After restart of VSD I was still able to upload error free with out any changes being made to my pages. I still went back through my pages and found one text box just touching a picture. Made adjustments that should keep that pesky thing away.

Hiya Eric,

I think they are asking you to do tickets for issues so they can get to them more efficiently while they are on holiday. I'm guessing it's much easier for them to see tickets than try to follow all the posts. Good luck on it

Thanks Eric for reporting this. We just became aware of this random error and will be looking into this.

I'm posting just as a update to this post. Though this error seems to be random, I'm getting close to being able to make it occur on demand. For me 95% of the time the error occurs when I'm working with text box's. I want to help CC get things running smoothly.

Merry Christmas CC

I haven't been able to get this to happen again since Scott offered the magical Christmas Egg to anyone who could reproduce it But in my case, it was definitely something to do with text boxes overlapping other objects. The first time it happened when I tried to put a link/button after a paragraph. When I moved the link into place the argument warning popped up. (I tried making just the last few words in the paragraph a link, but VSD insisted on all or nothing, so I made the link text separate from the paragraph, used advanced text, and placed it at the end of the paragraph). Had to ctrl-alt-delete and start over again.
So I made an actual button, made sure it didn't overlap the paragraph text box. But in shifting things around, the button touched the top of an HTML box (a form) and that argument warning came up so fast I couldn't move it away from the box or move the box away from the button, just ctrl-alt-delete again.

I have not been able to make it happen again, even when typing right over another HTML object or across another text box. I'll get the latest VSD7 update sometime over the weekend and see what happens.
Do you have the latest updated version installed?

Hi paintbrush. I grabbed the latest version the second it came down the tubes. I've now had the error show it's self but VSD doesn't lock up and I can still save. I'm getting close to being able to replicate this on demand but it may just be my setup.

I think I have this figured out. If you have a text box open (in red) and click anywhere off the edge of the page the Encountered an Invalid Arguement box pops up. It just happened to me twice in a row. I did hit the Alt button by mistake just prior to the first time, but not the second. Had to use Task Manager to close out of VSD and after the first time it told me my file was corrupted. Opened the latest backup copy and when working again, clicked off the page and up pops the error. I do have the latest update of VSD 7.0 installed released Dec 19th. I run Vista Ultimate with IE 8 as my browser.

Arrrrrghhh!! Mine crashed after a couple of hours building a new page on a site. CC VSD continues to frustrate with all of the problems it has. I had just finished entering text and had clicked outside of the box to get out of it and got the all too familiar "encountered improper argument" and could not get out of that - program crashed - I lost all my work. This is the latest version of VSD. My question is whether there is some type of auto-save feature built into VSD or not.

Yes, frustrating ain't it?
Were you unable to save some of the work? I normally do a "Save" after each page is edited or completed, sometimes after a big change on a page. (learned habit)

One more thing to add to the "Encountered Improper Arguement" thought. While working on my site yesterday, I again clicked off the text box accidently while it was highlighted in red. Fully expected the program to crash, but nothing happens. This is how the program crashed on me several times before.
The difference is now I have moved all the files into new folders for just the VSD 7 sites. Actually it seems like all my VSD 7 problems are gone now that I moved the files into new folders. Could it be that something in the VSD 6 files are corrupting files converted over to VSD 7?