my question is simple:
Is there anyway to generate the database sql creaton script from a Visio 2003 model?
I prefer Visio, however can be other program (freeware) that allows me to somehow agilize the process between the model and the sql code.
Thanks in advance!
I could be wrong, but I think the commands to generate DDL disappeared with Visio 2003. Apparently you now need the "Enterprise Edition" or some such dreck.
Also, this is a repeat of this question , and the original pointed to this free service: http://aboutwhatever.net/posts/visio-2007-database-model-ddl-generation
which does allow you to do what you want, with certain restrictions.
Once upon a time, there was Visio for Enterprise Architects.
There is a promising add-in for Visio 2010.
Related
So I have learned how to create a connection between AutoCAD and my SQL Server using the 'DBCONNECT MANAGER' tool within AutoCAD.
My next goal is to try and change the value/text of an existing label I have created in AutoCAD through an SQL update.
I am fairly experienced in SQL but I am very new to AutoCAD and the whole SQL-AutoCAD integration process in general.
I am setting up this question to ask if someone could point me the right way to achieving this SQL update.
Ultimately I want to be able to change the value of the label that is inside my AutoCAD project save from SQL.
Any advice/help/links/tutorials on this type of stuff would be extremely helpful as I have found very little on the web about this.
Thank you in Advance.
I know there are heaps and heaps of threads out there on recommending and using OpenXML to manipulate a Word 2007 (docx) document.
But none I could find, have a practical example (full solution in zip) that I am able to try out and demonstrate to learn quickly how to use OpenXML.
What I am after is a way to open a Word 2007 document template with several mailmerge fields, populate those fields from a dataset (SQL Server 2005) and save the template as a Word document ready to email.
UPDATE: We are using Visual Studio 2005 with .Net 2. Is that going to be a problem? Could we have .Net 3 installed but still use VS2005? Porting to VS2010 is in the cards for us, but not right now. We need a solution to this problem before we go upgrading to 2010.
And please do not recommend 3rd party products as we have to look for a free workable solution.
Much appreciate your time. Thanks
Here's an example.
It uses docx4j.NET - which is open source and which you can get from Nuget - not Microsoft's Open XML SDK.
I was trying to run a macro that was designed in for Microsoft Office 2003; however it will not work in Office 2010. Is there a wrapper or some sort of way that I can enable the Office 2010 to read the code?
Thanks for your help and please explain in layman's terms since I really don't have extensive programming knowledge.
You probably need to install the VBA Converter Pack. Follow the link at the top of the support page to download the hotfix.
http://support.microsoft.com/kb/926430/
I am now engaging in an excel vba project. It's a excel front interface for the workers in a site with an Access database in the company network. I dont like much the VBE in Excel 2007, so im wandering if I can do this with VB.NET, which seems to be a more adorable IDE. And where can I find some resources on this? Or recommanded books? Thanks!
Im using Excel 2007 et VB.NET 2008
You could also try Excel-DNA (free). There are many other products out there too. You can make it work with VB.Net Express also, you just need to add a reference to your excel SDK. Also, Add-in Express looks pretty nice. I've never tried it though (costs money).
I think you are looking for Visual Studio Tools for Office: VSTO.
This allows you to develop using VB.NET (or indeed C#) but with full access to the Office automation facilities.
The other day I tried out VS2010's SQL compare tools and thought they were awesome.
I am wondering if there is any way to harness these tools in code written in VS 2010.
Here is a MSDN forum thread about this. The answer points to this post which outlines how to use this via DTE. It is targeted at 2008 but I would think it is still applicable.