Hi Kotten,
What about ado transaction?
do u ever try to have more of one adodb.connection.transaction open with
ODBC SAPDB?
(annidate db transaction)

thank u

Max


> -----Messaggio originale-----
> Da: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Per conto di Koetter,
> Thomas Theodor
> Inviato: marted� 4 febbraio 2003 9.46
> A: '[EMAIL PROTECTED]'; Sapdb
> Oggetto: RE: Advice on Visual Basic with SAP DB Project
>
>
> Hi Girish,
>
> > -----Original Message-----
> > From: Girish Mohata [mailto:[EMAIL PROTECTED]]
> > Sent: Dienstag, 4. Februar 2003 04:44
> > To: Sapdb
> > Subject: Advice on Visual Basic with SAP DB Project
> [snip]
>
> > 1) This software will be a commercial product
> > being used by 8-10 accountants simultaneously over
> > a LAN. Are there any licencing issues that i need
> > to worry about in terms of paying fees for
> > installing the Database at my Clients computers
> > together with my VB application ? The application
> > will Not be open-source.
>
> Please see http://www.sapdb.org/7.4/sap_db_gnu.htm
> SAP DB's interface is LGPL, so you can combine it
> with closed source.
>
>
> > 2) My preffered choice of developement platform is
> > to use SAP DB as the backend and Visual Basic as
> > the front end. Connection through ODBC. However i
> > am open to other ideas like using Java with JDBC,
> > etc. Please advise me which option is best and
> > what are the trade-offs.
>
> There are many people using this combination VB/ODBC.
> The JDBC-driver is also applied in many projects.
> Advantage here is, that it is a pure Java implementation,
> that allows you to switch to other OS. In VB you
> stick on Windows.
>
> >
> > 3) In developing a data-driven software, my
> > attitude would be to run the business logic on the
> > server using triggers and procedures rather than
> > coding it in Visual Basic. In other words if i
> > wish to insert a record, i would do it by calling
> > a stored procedure and passing data values to it
> > from VB, rather than writing an SQL statement
> > through VB. Please advise on this. Any
> > comments/suggestions/experiences would be much
> > helpful.
>
> This is exactly what a German government department
> (Bundeskartellamt) did some time ago. They developed in
> VB/ODBC or ADO, respectivly, and SQL server. Due to
> having the business logic in the DB they could quite
> smoothly switch to SAP DB, where the client
> software wasn't changed at all, besides changing
> the connect string.
>
>
> Regards  Thomas
>
>
> ----------------------------------------------
> Dr. Thomas K�tter
> SAP DB, SAP Labs Berlin
>
>
> SAP DB is open source. Get it!    www.sapdb.org
>
>
>
> _______________________________________________
> sapdb.general mailing list
> [EMAIL PROTECTED]
> http://listserv.sap.com/mailman/listinfo/sapdb.general
>


_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to