Re: vb6 client server scenario
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Mon, 12 Oct 2009 11:49:42 -0500
"Gaanam" <gaanam.p@xxxxxxxxx> wrote in message
news:ce398f9b-2dfa-4091-aab3-645e47e64c19@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thank you all for the responses.
Ralph, you said it right. Provided, I am comfortable with VB6, Access
and related things, I just wanted a furtherance towards client-server
projects. It would have been an herculean task to switch to a whole
lot of new things at once. (Besides, months on end I was trying to
instal MySql and irritated with it, I felt its installation thingy is
purposely made to harras people rather than seek their satisfaction.
There are thousands of softwares that do a decent installation job,
then, what is wrong with the mySQL people? - similar experience with
PHP and Sun Products)
Coming back to the topic, I was lucky to find a whole lot of things on
planet-source-code.com.(64 pages of search results! and most of them
very very relevant) I wonder why google search does not show those
stuff. In fact I am making very rapid progress in my project.
Schmidt, I had downloaded the stuff suggested by you. Seems really
sophisticated. But to be frank, I could not understand a bit of it. My
fault, of course, May be I will look into it again once I grow little
more.
Anyway, Just curiosity, what are the cons of using MSAccess? I have
used it extensively with ASP and VB6, found it hassle-free.. What goes
against it?
Three questions, three answers follow.
[Mostly conjecture on my part - ie, personal opinion and observation, worth
about as much as any other personal opinion. <g>]
You will find that most open source is always a tad user-unfriendly when
compared to a Vendor's commercial product. It is just the nature of the
beast. Open source depends on what I call "Heros", that is to say, some
interested person or comittee, comes up with it, designs it, implements it,
and then provides it - "as is" with "some assembly required". Add to that
that most Open Source is designed to be "Vendor - independent", are most
often developed in Unix/Linix, and that most "Heros" have a distain for
Windows, for any language other than C/C++, and a real hatred of VB.
However, for all the popular Open Source products (MySQL, CVS, Subversion,
Open Office, PHP, ...) you will also find "Windows Heros" who provide help
with Windows. So using any Open Source product in Windows is often a
two-step process: First find the core libraries, second go hunting for a
Windows hero. Be aware that even these Heros will likely distain VB. <g> In
general it doesn't matter, their tools can be used no matter what language -
so don't go looking for VB specific instructions or components - go looking
for ActiveX and regular Dlls.
As for Google's search - something has changed over the last couple of
years - hard to put my finger on it, but IMHO I think Google is biased
against Windows, in fact anything Microsoft, and it shows in their results.
As for the pros and cons of using MSAccess (or rather a Jet formatted
database):
[a very short list - others will add I'm sure]
Con:
It is a file-based database. As such it has no defined interface nor engine,
ie, it is not a database server, for services it depends on an outside
manager - in this case the Jet engine.
In a distributed environment it suffers from the same issues that effect any
shared file or resource. The engine is very good at insuring data integrity,
but poor when it comes to things like transactions or concurrency.
While it is far more relational than other desktop databases available at
the time, it is still is essentially an ISAM-core technology that is 15+
years old.
It doesn't scale well. It still contains arbitrary limitations on sizes
wholly out-date with today's hardware. Limitations which in effect severly
limit its usefulness in certain environments. For example, a distributed mdb
file may support 12 users or 1000, it may run smoothly at a gig, yet
suddenly choke at 200 meg - it all depends on a multitude of factors - some
known in advanced, some only discovered at the last minute.
Anything other than OLE-datatypes (translate to VB) is an adventure.
It needs frequent cleaning.
Pro:
It has an excellent manager/designer - MSAccess.
There are a million articles on how to use it, maintain it, or abuse it.
It works damn well in its designed role as a simple desktop (or limited
shared) database.
-ralph
.
- Follow-Ups:
- Re: vb6 client server scenario
- From: Schmidt
- Re: vb6 client server scenario
- References:
- vb6 client server scenario
- From: Gaanam
- Re: vb6 client server scenario
- From: Ralph
- Re: vb6 client server scenario
- From: Gaanam
- vb6 client server scenario
- Prev by Date: Re: Array of pointers
- Next by Date: Re: vb6 client server scenario
- Previous by thread: Re: vb6 client server scenario
- Next by thread: Re: vb6 client server scenario
- Index(es):
Relevant Pages
|
