Posted by
sanjay minni-4 on
Nov 25, 2000; 7:34am
URL: https://forum.world.st/pl-recommend-r-dbms-file-manager-for-dolphin-4-tp3358276p3358309.html
Andy, [ I had started this subject before, so some matl. may be
rhetoric.]
Speed no issue so ODBC is ok but ODBC is a concern for admn.
i.e. clean install and uninstall and re-install and addl deployment files
At present we use Sybase Adaptive Server Anywhere 6.0(ASA 6)
ASA has an "embedded SQL interface" which consists of .h header files
and import libraries .lib for Watcom C/C++, MSVC++, Borland C/C++
...and here is some addl info from the manual.
Q.Primafacie can it be used with Dolphin to deploy apps
(I know little about lib/dll etc so far mostly working with a RAD
on Win and 3GLs in DOS)
info from manual...>>>
...Alternative to using import library...loading ASA interface lib
dynamically w/o
linking against import library...
use esqldll.c
1. your program must call db_init_dll lo load DLL ...and db_fini_dll to
unload
2. #include esqldll.h
3. compile esqldll.c ...(I have all the reqd c/c++ compilers)
4. link your object module to esqldll.obj
>>>... end info from manual
If I can get some indication that this can be used with Dolphin then I will
try to
go farther into it.
The current release ASA 7 has OLE DB / ADO, but that would mean Larger
deployment size and is the other alternative
Regards
Sanjay Minni
"Andy Bower" <
[hidden email]> wrote in message
news:8vlqgn$53159$
[hidden email]...
> Sanjay,
>
> > I want to know what products typically are used with
> > Dolphin 4.0 to store data as Files or as an RDB(MS) and
> > which has a small footprint for deployment on the web
> >
> > If an (R)DBMS / File Manager product typically gives .lib or .dll
> > to be interfaced with MSVC or WC++ or CPP then can it be
> > interfaced to Dolphin in the same way
>
> When interfacing with an RDB you typically have several choices.
>
> 1. The first is to use the Database Connection package that is available
in
> Dolphin Standard Edition. This allows you to connect to any database that
> supports an ODBC driver (most do). The old disadvantage of this is that
ODBC
> intefaces *tend* to be somewhat slower than native direct access. A great
> advantage, of course, is that you can defer (or change) your choice of
> database and your code will continue to be compatible.
>
> 2. The second is again to use Microsoft's Active Data Objects (ADO)
> technology. This is a framework which can access any ODBC data source
(same
> limitations as above) and also any OLE DB data source. Some DB providers
> supply an OLE DB interface to theire products and this is typically faster
> than the equivalent ODBC driver. Dolphin does not come with an ADO
framework
> built-in, however, it is trivial to auto-generate all of the ADO
interfaces
> classes using the ActiveX Component Wizard. You may then need to spend
some
> time adding some "sugar" methods to make these generated interfaces more
> Smalltalk friendly. This is not essential, however, and the classes could
be
> used directly.
>
> 3. The third alternative is to link straight to an RDB's native access
DLLs.
> We don't support access to LIB files but basically you can fairly easily
> access any external DLL. Details are at:
>
>
http://www.object-arts.com/EducationCentre/Overviews/ExternalInterfacing.htm>
> The results will typically be fast but not portable to other databases
> should you wish to change in future. Personally, I would go for either 1)
or