p2p.wrox.com Forums

Need to download code?

View our list of code downloads.


  Return to Index  

pro_vb thread: Network Application in VB


Message #1 by Prashant Shinde <pds_shinde@u...> on 15 Apr 2001 23:55:13 MDT
If you're not married to Access because of forms or reports, you might look
into using MSDE instead.  A much cleaner solution for most instances.


-------------------------------
Christopher Tacke, MCSD
Associate, Rubicon Technologies
(xxx) xxx-xxxx  ext 319

-----Original Message-----
From: Chris Ellegood [mailto:jcellegood@h...]
Sent: Monday, April 30, 2001 11:54 AM
To: professional vb
Subject: [pro_vb] RE: Network Application in VB


Hmm... True... I wonder if he could have set queries in the access database
that would narrow down the table and then he could just open the queries
instead.

Thanks.

Chris Ellegood, ATP,  xxx-xxx-xxxx

----- Original Message -----
From: "Chris Tacke" <ctacke@r...>
To: "professional vb" <pro_vb@p...>
Sent: Monday, April 30, 2001 10:44 AM
Subject: [pro_vb] RE: Network Application in VB


> Be aware that this causes a LOT of network traffic.  Access, unlike SQL
> Server will marshall ALL data to the client, essentially sending a full
copy
> of any table used to the client machine.
>
> For instance, if you have a customer table with 100,000 rows and you run
the
> following SQL:
>
> SELECT * FROM Customers WHERE LastName LIKE 'John%'
>
> If there are, say 100 rows that meet this criteria, SQL Server filters the
> data and sends the client 100 rows.  If you're using Access, it will send
> you all 100,000 and then the client filters it down to 100.
>
> This can be a huge problem if you have a lot of users or limited
bandwidth.
>
>
> -------------------------------
> Christopher Tacke, MCSD
> Associate, Rubicon Technologies
> (xxx) xxx-xxxx  ext 319
>

  Return to Index