Another Aaaarrrghh

Yes, the common dialog requires that a development environment be installed. Really annoying isn’t it?

Some other scripts have been written like this. And all you can do is ask them for the path of the file (as best as I know). I converted the scripts to plug-ins to work around this issue.

Richard

Not specifically a 3DC issue, another vbscripting bit..

On one machine (win2k) the line

Set CommonDialog = CreateObject(andquot;MSComDlg.CommonDialogandquot;)

has no problem, when I transfer the script to another Win2k machine it doesn’t work…

Printing the error number gives : -2147221230
Same with the .x exporter script

Any idea what is missing from the second machine ?
Only difference I can tell is that the working machine has visual studio installed , the second doesn’t.

[edit] For info, if anyone gets this, I managed to fix it by installing VB6! A bit extreme I know, but if anyone knows a better source for required DLL(s) I’d love to know.

Try looking at the code around that general area. It could be something else causing the error. I’ve noticed debugers can be confused easily at times.

Oh, I just noticed your post script. Yeah, updated dll’s and other system resources can help with some problems too.

I’ve discovered that the object that is initialised in the script is only usually installed with either VB, or visual foxpro. As soon as I installed VB it worked as expected.

I’m going to have to include some code to do something like pull the group name as a default filename if the dialog cannot be initialised.

I think I remember a post about updating the common controls dll. Richard gave a link to microsoft to do this. I’m not sure if this will solve you’re particular problem, but at least it can give you a direction to explore.