{{tag>category:"OpenInsight 32-Bit" author:"Barry Stevens" author:"Pascal Landry" author:"Warren Auyong" author:"Mike Ruane"}}

[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]


==== Visual Studio 2005 (OpenInsight 32-Bit) ====
=== At 12 DEC 2005 07:38:34PM Barry Stevens wrote: ===
 
 
<QUOTE>
Could anyone tell me what the development time factor might be in developing a large business database system using visual studio 2005 compared to using openinsight. eg. twice as fast in OI or three times faster in Visual Studio.



Thanks
</QUOTE>
----

=== At 13 DEC 2005 10:19AM Pascal Landry wrote:  ===

<QUOTE>It all depends on how savy you are in each environment.



I just created a form to edit a Sql database in OI in 30 minutes complete with popups.



I spent at least twice that amount of time yesterday jugling with sqladaptors and stuff in Visual Studio .net 2003 and didn't accomplish anything.



Pascal

</QUOTE>

----

=== At 13 DEC 2005 05:05PM Barry Stevens wrote:  ===

<QUOTE>Cool... thank you

</QUOTE>

----

=== At 13 DEC 2005 06:18PM Warren Auyong wrote:  ===

<QUOTE>Visual Foxpro is probably the way to go if you're talking large databases on Microsoft platforms. Attaching to SQL server is pretty much a matter of defining the data sources and designing on a client server model.



Given equal skill levels of the developer I'd probably give Foxpro the edge because VFP is a much more mature product. The ability to create reusable inheritable object classes on a wide scale is a major timesaver.



I couldn't quantify development time difference. Again it depends on the skills of the developer and the nature and complexity of the application.

</QUOTE>

----

=== At 15 DEC 2005 02:37AM Barry Stevens wrote:  ===

<QUOTE>Thanks, but the reason for stating Visual Studio is that i am competing for a quote using openInsight , against an inhouse development option - using Visual Studio.

</QUOTE>

----

=== At 15 DEC 2005 08:07AM Mike Ruane wrote:  ===

<QUOTE>Barry-



The issue with using a development tool that is not tightly coupled to the database platform is that a change to either side (a new version of VS, a new release of SQL) may cause the application not to work, or create the need to upgrade both instead of one. There is alway the backward compatibility issue as well- .net 1.1 is not compatible with .net 1.0, and version 2.0 is not compatible with 1.1 !



Because our toolset is designed to work very well with our database, and in fact our database is used by our development tool, you can always count on compatibility. And because we don't have to worry about trying to be a front end to all back ends, we focus on on core strengths and as a tool are very good at what we do.



Hope this helps-



Mike

</QUOTE>

----

=== At 17 DEC 2005 11:12PM Warren Auyong wrote:  ===

<QUOTE>Visual FoxPro at one point was part of Visual Studio and is still considered an add-on.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=AAA22F9D30F9EEEB852570D600038824|View this thread on the Works forum...]]