Simon, you ROCK! That worked! I am extremely gratefull to you.

TFD

"LineVoltageHalogen" <tropicalfruitdrops (AT) yahoo (DOT) com> wrote

No particular reason - in this case it doesn't matter, but it others it may,
so I generally use the extended objects if there is one.

As for resources, I've only ever used Books Online (and Google, of course).
I usually work with SQLDMO in Python and VBScript, and it isn't too hard to
use VB code as an example.

Simon

Simon, one quick question. Does the Java programming language support
SQL-DMO? I was thinking that if I wanted to convert my c# program to
J2EE could it be done?

TFD

No idea. If you can access COM objects from Java, then I don't see why
not, but I don't know how you would do that.

In any case, I'm not sure what the point would be - anyone running
MSSQL must be running Windows, so there's not much benefit to a Java
version. Even if an organization uses Java on Unix/Linux for business
applications with an MSSQL backend, the MSSQL DBAs will still be using
Windows, and SQLDMO is most useful for them.

You might also consider that the SQL2005 version of SQLDMO - SMO - is a
..NET assembly, not a COM object, so .NET is the way to go if you intend
to support SQL2005 at some future point.

Simon

Good points, all of them.

As a side note I managed to finish my application entirely in C#. I
was hard not having any examples and not being a programmer. All the
VB examples out there helped quite and bit as well as your input.

Thanks Again, TFD.