Re: Namespaces? Why?


"Jerry Stuckle" <jstucklex@xxxxxxxxxxxxx> wrote in message
news:wLadnevBs7BCPJ_anZ2dnUVZ_tjinZ2d@xxxxxxxxxxxxxx
Steve wrote:
"Jerry Stuckle" <jstucklex@xxxxxxxxxxxxx> wrote in message
news:Qu2dndheJM6izJ_anZ2dnUVZ_vLinZ2d@xxxxxxxxxxxxxx
Steve wrote:
"Jerry Stuckle" <jstucklex@xxxxxxxxxxxxx> wrote in message
news:7KKdnSei3tvGMpzanZ2dnUVZ_vqpnZ2d@xxxxxxxxxxxxxx
Jim Carlock wrote:
"RageARC" wrote...
using namespace curl;
init...
exec...
close...
That looks like Visual Basic 3/4/5/6...

Dim db As DAO.Database
Dim rs As DAO.Recordset
Dim sSQL As String

sSQL = "Select * From customers;"
With DAO
Set db = .OpenDatabase("mydata.mdb")
Set rs = .OpenRecordset(sSQL)
End With

'... rest of the code

Except I think it works a little better with the "With" in
Visual Basic.

What's the advantage of a namespace if you have 5 different
databases to connect to?

Absolutely nothing. Namespaces are for source code separation, not
database selection.
jerry, i think he meant the DAO used in the 'with' statement...which is
NOT a namespace but an object instance. i believe his code sample above
would fail anyway since i don't recall DAO being a static class -
static was introduced to vb in vb.net.
OK, that makes sense. Not being familiar with DAO, I wouldn't know (or
care ;-) ).

dude, all he had to say was 'vb' and i completely lost interest from
there. ;^)


:-) Unfortunately, I need to do some VB work still.

don't get me wrong...i use vb.net all the time. however, it's more like a
programming language than whatever they call vb < .net these days.

what's worse is that he's probably more likely using vb 3/4 since data
access objects were obsoleted in later versions for the alimighty
(laughs) adodb class(es). that would also explain why he has no idea that
dao.interface is not the same as namespace::resource

later.

Yep, I understand. I use the adodb interface in VB, though - it really is
better.

worlds better...just don't bind form controls to it. vb.net's adodb is
supposed to have fixed all the crap that happened doing that in the past.
however, i was so frustrated with 'the past' that i still keep a middle man
(my o.m.) inbetween the ui and db layers.


.

Relevant Pages

  • Re: Namespaces? Why?
    ... Dim rs As DAO.Recordset ... With DAO ... statement...which is NOT a namespace but an object instance. ... alimighty adodb class. ...
    (comp.lang.php)
  • Re: Namespaces? Why?
    ... Dim rs As DAO.Recordset ... With DAO ... What's the advantage of a namespace if you have 5 different ... adodb class. ...
    (comp.lang.php)
  • Re: Namespaces? Why?
    ... Dim rs As DAO.Recordset ... i think he meant the DAO used in the 'with' statement...which is NOT a namespace but an object instance. ... I use the adodb interface in VB, though - it really is better. ...
    (comp.lang.php)
  • Re: Namespaces? Why?
    ... Dim rs As DAO.Recordset ... i think he meant the DAO used in the 'with' statement...which is NOT a namespace but an object instance. ... I use the adodb interface in VB, though - it really is better. ...
    (comp.lang.php)
  • Re: Namespaces? Why?
    ... Dim rs As DAO.Recordset ... With DAO ... What's the advantage of a namespace if you have 5 different ... fail anyway since i don't recall DAO being a static class - static was ...
    (comp.lang.php)