Re: Any PB & ADO gurus?
Michael J. Sabal wrote:
>Why not use ODBC?
Bernie Ryan wrote:
>Did you look in the archive...
don cole wrote:
>I found the best way [is to] start all over with Euphoria.
Thanks for the responses guys. I haven't used ODBC in over ten years, in
VB6 I pulled info from ODBC and just did direct ADO. If I remember it was
because of the performance hit using ODBC. Bernie, in the time honored
tradition of programmers everywhere, I was trying to be lazy and here you
give me homework to do 
Don, I've been looking for over thirty years for the 'ONE TRUE LANGUAGE' a
bit like Don Quixote. I'm a true believer because I see glimpses of it
and know I in theory could get what I want. Euphoria is so close, but it
continues in some traditions that I am dead set against.
Don ya push my button and I feel a rant coming on...
I hesitate to commit to Euphoria partly because I would never deliver a
product I couldn't be confident in. This DLL I wrote works and I've used
it, but for reasons I don't understand, it blows up when called from
Euphoria. Not that it's Euphoria's fault, frankly I'm amazed I was able
to use an ADO object from PowerBASIC at all. I wasn't expecting it to work,
but it did and has been rock solid in several other projects I've done.
PowerBASIC is out, because although it does some things I need, it's ugly
(which makes it difficult to read) and doesn't do all that I need.
Another thing (again not the fault of Euphoria) is I wrote a windows program
right after my skipper submission using win32lib. When I updated to a newer
version of win32lib my program didn't work anymore. So I won't use win32lib
because I don't trust it to not break my program in the future. I've had
this problem with updated controls for VB6 as well. I don't buy those
controls anymore either. Now I just write my own (where I can.)
People have ideas all over the map. This discussion of namespaces caught my
interest because it's a good example of solving the wrong problem. Name
collisions don't happen with the right scoping rules. OOP is overhyped,
but being able to create instances of a class completely eliminates this
problem in a way that makes enterprise level development very managable.
I maintained over a million lines of VB6 code (by myself during some of
it's ten year life) which I couldn't have done without the project's file
level scoping rules and the IDE allowing me to immediately drill down to
the definition of any routine or variable in two clicks. Having to search
for the declarations with no idea of what file it's in ridiculously slows
down productivity. You demonstrate a problem in a program I've never seen
before written in VB6 and I can track it down in the code in just a few
seconds (it may take longer to actually fix the problem, but finding it is
usually trivial.) I can't live without that anymore. I'm old and cranky.
... and that's the end of my rant.
ken.
Now I've got to do the homework Bernie gave me.... sheesh...
|
Not Categorized, Please Help
|
|
