![]() ![]() Indeed this takes me back to the old days about 20 years ago of messing around with ODBC drivers. It really isn't intuitive that you need to use a different ODBC Driver (the Generic one) in the Reverse Engineering operation. Once the source connection is tested, it's fair to say that it works. ![]() Not sure why this is not a smoother operation, but then anything involving ODBC never has been! It might depend on what version of SQL you are running as to which ODBC driver you use to set up the data source. I used the Generic ODBC Driver in the connection action in Reverse Engineer and despite it flagging a warning, it worked. I had already set up the data source using a SQL Server ODBC Driver (native 11) - after a lot of rigamarole. I decided on a whim to try to connect using the ODBC Generic Driver instead of the one for SQL Server. OK, so I couldn't wait on a solution to fall out of the sky, haha, so I kept looking at what I found and finally worked it out after re-reading the documentation page here: After a day and a half of this, I thought I would share this solution or workaround, rather. Build and validate diagrams that support industry standards, including BPMN 2.0 and UML 2.I hope that this helps someone who is out here stumbling around trying to figure this out.Create professional diagrams easily with ready-made templates and shapes.PC: 2-core 1.6 GHz processor - 4 GB, 2 GB (32-bit) RAM - 4 GB of available disk space - 1280× 768 screen resolution - DirectX 10 graphics card for hardware graphics acceleration ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |