Re: Databases - DAO and ADO

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Olaf,

Last night I downloaded the files and demos from your weblink and have read
the readme files (except the one I think is in German ;)

I was very impressed with the speed comparisions between the ADO and SQLite.
Very impressed. Zoom zoom.

I'll have to admit though, I was totally overwhelmed by it all. Why? Because
I'm still at rung #2 on my climb to becoming a proficient VB programmer.

I'll be looking at the Metastock demo in a few minutes, but I thought I'd
drop in and read some more of the comments in this thread.

I'm concerned as to how long it would take me to learn how to use SQLite
with my lack of database and SQL experience. I've got a time crunch to get a
nice quick data retrieval piece of code completed (with NO storage
requirement, by the way). I still have to write the code that will be
manipulating the data retrieved in various ways, so the sooner I can get a
data retrieval and query coded the better. Can a complete newbie greenie
like me learn how to do this with SQLite in a speedy fashion? Is there a
SQLite for total Dummies write-up that I missed somewhere?

With all that said, I have to say that from what I saw it is a very nice
piece of work Olaf. Kudos!

Cheers!
Webbiz




"Schmidt" <sss@xxxxxxxxx> wrote in message
news:ek5kM$PvJHA.5684@xxxxxxxxxxxxxxxxxxxxxxx

"Cor Ligthert[MVP]" <Notmyfirstname@xxxxxxxxx> schrieb im Newsbeitrag
news:%23%23HfAOMvJHA.4476@xxxxxxxxxxxxxxxxxxxxxxx

Why do you not make the OP attend on the recordset.
What do you mean with that?
The Example I've posted does work with Recordsets.
And yes of course, Recordsets are nice "2D-Containers",
which are easy (and fast) to pass around using only an 4Byte-
ObjPtr - sortable by more than one Column, easy bindable
to GUI-Controls which support these Containers, etc.

A much more VB6 like method then using SQL ...
Recordsets are usually retrieved over SQL - but why only
use plain (and dumb) "Select * From Table"-queries?
SQL has a lot more to offer - so why not use that builtin
"dynamic Query-Compiler" which is able to interpret and
process your SQL-Textstring "on the fly"?.

And @Ivar:
That's exactly the main-advantage over an array-based,
"handcoded" solution - you don't need much code and
efforts, to build a flexible "query-gui" for your customer,
which offers a whole lot of filter-, aggregation-, calculation-
and grouping-options, just by concating the appropriate
SQL-string-parts.
You cannot achieve the same flexibility with a handcoded
solution - Ok, you can ;-) - but with much more lines of
code.

(Although in the latest version of VB, I would go for
LINQ to SQL, but that is not the solution for the OP
in my idea)
Yep, that's the wrong group for these recommendations -
but you know that of course.
And BTW, we had these: "the power of LINQ" discussions
already in the german classic-groups - and so far nobody of
the .NET-folks came up with a LINQ-based example, which
was able to demonstrate the "increased productivity" (with
less lines of code, compared with a plain Recordset+SQL-
solution in VB-classic).
Maybe you want to post another one.

It would be better in my idea to tell the OP that a database
server or a database engine (by instance Jet) uses tables.
I don't get you here - each SQL-based engine supports
something like "tables".

The tables can be used in a recordset from VB6 simple
by First, Next, AddNew and more as those methods ...
DB-Tables are just "raw quantities" - and the words you mention
here are not related to these "tables" - these are methods on an
Obj-Representation - an resultset/recordset - which normally
represents only a subset and/or a combination of the table-data
from your "raw-quantities".

(We find that back in Linq to SQL again where those methods
are used in quiet similar way, but that is not VB6).
Sorry - but if you mean Recordsets+SQL (or your repeatedly
mentioned "LINQ to SQL") is there, to allow just a recordbased
navigation on a "plain DB-Table", then you should really work
with Arrays instead - you can write them to disk with 3 lines
of code (at least in VB-Classic) and read your "table-arrays"
from there with another 3 lines. ;-)

That kind of table handling is much easier then using an
Array like in history.
As just said, if you think about DBs in that simple way, only as
a bunch of tables - and a Recordset only as a Navigation-
Helper on a plain table - then indeed - good old Array-
Handling would be the way to go - no need for a DB... <g>

Although I am more active in newsgroups about new VB
languages, ...
Then I'd recommend to stay there ...

...outclasses the VB6 methods in my idea that approach from
1970 which you show.
This sentence is just ... sorry, I don't know what you want to say.

SQL server Express is free,
Yep, it is free - and crippled regarding multiuser-performance -
difficult to install - the deployment-volume alone for the clientside
access-layer is around 4MB - the serverside install is even larger -
moving around your DBs is not easy (they need to be attached/
detached to/from a running server-instance) - not very easy to
use in a simple desktop-scenario if you ask me.

Olaf




.

Relevant Pages

  • Re: Is it just me, or is Sqlite3 goofy?
    ... be saying it has gasoline engine. ... SQL database, with an SQL engine. ... criticisms directed at SQLite. ...
    (comp.lang.python)
  • Re: MVPs, Points, OP, etc.
    ... should learn how to use SQLite for my particular VB6 ... SQLite - when used over ADO-like wrapper-classes would ... When this switch is Off - then you compare more the engines ... just start with SQL and classbased DataAccess-Layers. ...
    (microsoft.public.vb.general.discussion)
  • Re: MVPs, Points, OP, etc.
    ... should learn how to use SQLite for my particular VB6 ... SQLite - when used over ADO-like wrapper-classes would ... When this switch is Off - then you compare more the engines ... just start with SQL and classbased DataAccess-Layers. ...
    (microsoft.public.vb.general.discussion)
  • RE: ado connection to access vs. sql server?
    ... > data in multiple files, which needs quite careful tracking, several ADO ... > connections and many recordsets. ... > I need to perform quite tricky calculations (too tricky to be done using SQL ... > be kept practically in Excel workbooks). ...
    (microsoft.public.excel.programming)
  • Re: Operation is not allowed...
    ... Your original problem stemmed from using an ADODB.Recordset object to commit ... Recordsets are for *retrieving* data, ... backed by some of the worst SQL 2000 database design I've ever ... Well, instead of going back, fixing the typo and fixing ...
    (microsoft.public.inetserver.asp.general)