Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #6838 > unrolled thread

DBF 2 SQL

Started by"Marc Verkade [MITCon]" <marc@mitNOSPAMconDELETE.nl>
First post2014-05-11 06:18 +0200
Last post2014-05-14 10:47 +0200
Articles 4 — 4 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  DBF 2 SQL "Marc Verkade [MITCon]" <marc@mitNOSPAMconDELETE.nl> - 2014-05-11 06:18 +0200
    Re: DBF 2 SQL Sherlock <sherlock@sherlock.com.au> - 2014-05-11 06:16 -0700
    Re: DBF 2 SQL "Willie Moore" <williem@wmconsulting.com> - 2014-05-13 14:08 -0500
    Re: DBF 2 SQL "Er!k \\/!$$Er" <nospam@nospam.url> - 2014-05-14 10:47 +0200

#6838 — DBF 2 SQL

From"Marc Verkade [MITCon]" <marc@mitNOSPAMconDELETE.nl>
Date2014-05-11 06:18 +0200
SubjectDBF 2 SQL
Message-ID<536efa30$0$3726$6d5eeec5@news.sunnyusenet.com>
Hello all,

It has been a while since I had to do serious VO development but now I am 
asked to port Bake-it to SQL, so here I am again....
So... hai to all the old people still knowing me around here.

I have been studying the efforts done by various other people and have gone 
back to 2006 in this newsgroup to find do's and don'ts

There are 2 aproaches it seems: VO2ADO and direct SQL
Ginny and Willie went the VO2ADO way and Geoff the direct SQL among others.

I have made the decision to use VO2ADO since it integrates better into the 
existing DBServer classes.
Perhaps somebody has some advice and/or a DBF 2 SQL tips and tricks sheet?
I will be very happy if somebody can help me to navigate around some quircks 
which probably are there...

Thanx, Regards
Marc Verkade 

[toc] | [next] | [standalone]


#6839

FromSherlock <sherlock@sherlock.com.au>
Date2014-05-11 06:16 -0700
Message-ID<863564da-34df-40e8-afce-52682533b1da@googlegroups.com>
In reply to#6838
Marc

snip[ I am asked to port Bake-it to SQL, so here I am again....]

We went the DBF/FPT to POSTGRES route and I used in my desktop conversion ODBC and a wrapper around Dbserver to create all the CREATE SQL and INSERT and ton of other custom code, convertiing memos and arrays and encrypted data... from 100;f or sites with up to 12 years history. Basically use the DBserver classes to access data and mould it to the new future. This was a one way convertion, and then POSTGRES using .NET connectors or others wrappers for the new app.  

The reason for Postgres was previous excellent experience with 2 other applications over about 8 years, multi platform, web hosted or desktop solution. 

Write a windows app or web app around the same data and deploy to say Amazon service which has out of the box support for Postres. Also with a big move to JSON over XML with interchange of data it has native JSON support.

Also FREE licensing for personal, development and commercial applications.
ONe of my competitors with the EXPRESS MS sql when they hit the data limit it is $1200 and $330 per user to upgrade licensing.

Phil

[toc] | [prev] | [next] | [standalone]


#6840

From"Willie Moore" <williem@wmconsulting.com>
Date2014-05-13 14:08 -0500
Message-ID<lktqj2$348$1@speranza.aioe.org>
In reply to#6838
Marc,

I did go for the VO2ADO method but I also wrote SQL statements instead of 
just opening up the entire table like you would a DBF. That gave me a lot of 
performance benefits but the downside is that you cannot just browse an 
entire table at once. VO2ADO is very easy to use. I have never used the RDD 
version, I found it much easier to use the ADOServer class or ADORecordset 
class directly with a SQL statement. ADOServer is a drop in replacement for 
DBServer. It can also be used with bBrowser.

Regards,
Willie
Vulcan VIP 

[toc] | [prev] | [next] | [standalone]


#6841

From"Er!k \\/!$$Er" <nospam@nospam.url>
Date2014-05-14 10:47 +0200
Message-ID<lkvaht$2tdj$1@adenine.netfront.net>
In reply to#6838
Hi Marc,

If you are planning to use MS-SqlServer you might want to consider this:

http://msdn.microsoft.com/en-us/library/ms810810.aspx
("After SQL Server 2012, the SQL Server Native Client OLE DB provider will 
no longer be included in SQL Server Native Client.")

You can however use the OleDB provider for ODBC to connect to the database

regards,

Erik




"Marc Verkade [MITCon]"  schreef in bericht 
news:536efa30$0$3726$6d5eeec5@news.sunnyusenet.com...

Hello all,

It has been a while since I had to do serious VO development but now I am
asked to port Bake-it to SQL, so here I am again....
So... hai to all the old people still knowing me around here.

I have been studying the efforts done by various other people and have gone
back to 2006 in this newsgroup to find do's and don'ts

There are 2 aproaches it seems: VO2ADO and direct SQL
Ginny and Willie went the VO2ADO way and Geoff the direct SQL among others.

I have made the decision to use VO2ADO since it integrates better into the
existing DBServer classes.
Perhaps somebody has some advice and/or a DBF 2 SQL tips and tricks sheet?
I will be very happy if somebody can help me to navigate around some quircks
which probably are there...

Thanx, Regards
Marc Verkade 


--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web