-=> Quoting Neil Heller to Frank Swarbrick
 NH> I couldn't tell you.  I would think you would have a hard enough time
 NH> finding ANYTHING for VSE nowadays.
:-)
 FS> You write the programs in whatever language, with embedded
 FS> SQL calls, right?  Then you run them through the SQL preprocessor
 FS> which translates them into language calls.
 NH> That's the theory.  First you create the source code program with the
 NH> embedded SQL and call that module something with a different extention
 NH> (*.SQL?).  Then run it through a special preprocessor which converts
Not necessarily.  *.SQC for C code.
 NH> the SQL calls into something your compiler can handle and names the
 NH> resulting file *.C (or maybe *.CPP if you're lucky).  Then you compile
(You can always override the compiler to tell it, "Yeah, this is actually
C++, nevermind the actual filename")
 NH> with your regular compiler.  If something is amiss however, you have
 NH> to go back to step one and work only with the *.SQL file.  As a result,
 NH> error messages from the compiler are next to useless (especially if
 NH> you're using many include files).
Then you're using a bad preprocessor.  Take a look at the output of the
preprocessor - it uses the #file and #line directives to tell your C/C++
precompiler that it's really in this other file over here.  The error
messages then become perfect rather than "useless."
 NH> A far more civilized approach is to use ODBC (which was developed for
 NH> just this sort of occurrence).  It is yet another language, but a LOT
 NH> simpler.  The ODBC calls are placed into your C/C++ source code but
 NH> you only have to compile once.  There are many books out about ODBC;
 NH> the one I used is called "USING ODBC2" by Que.
Well, I'd disagree about using ODBC, but to each his own.
 NH> Correct, you must first create the database (structure, links,
 NH> indices, etc.) with the native database tool.  I _think_ that Access
I don't think so - I'm sure you can issue ODBC commands to Access or whatever
to create the database...
 NH> complete poop on that; MS on-line documentation is VERY extensive,
 NH> also. 
Extensive, yes.  Accurate - when you're lucky, especially on their older
products.
... I am Drunk of Borg. Resultance is floor tile.
--- FastEcho 1.46
---------------