>Don't you want to re-write it in .NET as well? I saw the question asked recently on ASP.NET/Forums and I even did a bit of research into it.
>It's quite easy from .NET, let me know if you need more info.

No, I want to keep it in VFP, since I'm using .DBFs to store my schema change scripts.

~~Bonnie





>
>>Hi gang,
>>
>>We have a little VFP utility I wrote about 6-7 years ago to automate and version the creation and updating of SQL Server databases. It uses SQL-DMO.It works great with SQL 2000 & SQL 2005. Last week, someone in our company decided that we needed to certify that our .NET applications (and this utility) were compatible with SQL 2008.
>>
>>What I didn't realize is that DMO had been deprecated in favor of SMO with SQL 2005. So now, SQL 2008 doesn't come with DMO and a "compatibility pack" is needed to install DMO. Our installation guys don't want to have to rely on that compatibility, so it looks like I'll need to re-tool my VFP utility to use SMO now (I haven't had to update the utility in years, it works so good <g>). My question is this: is it going to be a fairly straight-forward process? Will a lot of the same funtionality exist and it will just be a matter of using the SMO object instead of the DMO object (with maybe some additional minor tweaking)?
>>
>>I know that I should just test it out myself, rather than ask these silly questions. I always say that to myself when other people ask these types of questions (can blah-blah-blah do this? well, try it first silly!! <g>) ... but, hey, it's a weekend and I just thought I'd throw it out here to give myself a headstart before the work week. <g>
>>
>>Thanks!
>>~~Bonnie