Network traffic

  • Thread starter Thread starter Phil Hunt
  • Start date Start date
P

Phil Hunt

I have a VB app using ADO/ODBC to access an MS Access database over LAN.
Everytime I update or insert to a table, the network light (in the system
tray) does not go off, telling me it is still sending/receveing some kind of
network message. How can I stop that ? (I always start transaction and
commmit during update)
 
I forgot to mention that I kept the connection open on purpose to improve
the performance. So the light never go off. My basic question is "what is
the best way to do improve this kind of application"

Thanks
 
Phil, if you ask a question about network lights, most folk will probably
think that you are asking a question about network lights!

Apparently not.

Your new question is: "What is the best way to .. improve this kind of
application"?

What can I say? Make it lighter, cheaper, stronger, & available in a wider
range of colours!

Phil, seriously, no-one reading this newsgroup, has the faintest clue what
your application actually does. No-one has the faintest clue what you mean
by the term, to "improve" it. You'll need to give us more information before
we can possibly help you.

It's like me asking you: "How can I make my house better?" Since you don't
know anything about me, or my house, or my lifestyle, how could you possibly
answer that question?

HTH,
TC
 
Hi TC,
My second question sounds obscure only because I made reference to my first
question without quoting(?) it.

My basic question is:
I have a VB client/server app sharing a Access 2K db, I have to keep the
connection to Access opened all the time to get acceptable performance. Is
there any better way to do this without this brute force method. I thought
having the network sending/receving packet constantly is bad.
 
Aha! Now I see what you're asking. A good way to keep the connection open is
to use the DAO OpenDatabase method to establish a connection to the
database. In an >Access< app which was split into a "programs" database and
a "data" database, the code is:

dim db as database
set db = dbengine.opendatabase ("full path to data database")
' keep the db variable "in scope"
' for the whole of the run; then:
db.close
set db = nothing

Not sure what that would be in a VB app. Probably very similar?

Keeping the db open - or similar techniques, like keeping a >table< in the
db open - will >not< result in the network constantly sending or receiving
packets, AFAIK. So there must be some other cause of your network light
staying on continuously.

HTH,
TC
 
Back
Top