slow compilation

[angelica]

Hey,

I have a laptop with processor Centrino 1.6 Ghz and I am programming a VB.Net (ADO.Net) and have a back connection to Access. The connection is very slow.

Can anyone tell me if I get laptop with a multi-threading Pentium4 Processor will help?? Thanks

[Calibra]

Hey,

I have a laptop with processor Centrino 1.6 Ghz and I am programming a VB.Net (ADO.Net) and have a back connection to Access. The connection is very slow.

Can anyone tell me if I get laptop with a multi-threading Pentium4 Processor will help?? Thanks


if you mean that youre acces backend is not on youre laptop, then it's not gonna help you an bit.

I guess the slow connection is youre bottleneck, but you can always buy an other laptop and donate this one to me for the advise :D

[Dave Sell]

I highly doubt a faster CPU will solve your problem.

[Pino]

I've moved this to the General Pc Forum, i feel you may get a better responce here :)

[angelica]

let me explain my problem well. At the moment I only have one connection running. I am connecting to Access on my computer as a localhost. When I rebuild the solution and get a connection this is very slow. Thus a hyper-threading CPU with a better speed help? I mean a Intel Pentium 4 with 3.0G give me a faster connection??

[Dave Sell]

No. This sounds like a network bottleneck.

[Kasracer]

No. This sounds like a network bottleneck.
He's using access via localhost. He's doing it internally which means it doesn't leave his NIC.

As to the poster, I have no idea. It might help or maybe there is a leak or some obscure bug or something you forgot to do. I don't know VB.Net and/or access very well.

[Dave Sell]

He's using access via localhost. He's doing it internally which means it doesn't leave his NIC..
I stand corrected.

[plenderj]

If its running off the localhost, I'd say its an issue with your code...

[dglienna]

i have a somewhat similar problem. as the program connects for the first time, there is a considerable lag before the adodc form opens. once it is connected, all is good.

[RobDog888]

i have the same problem. as the program connects for the first time, there is a considerable lag before the adodc form opens. once it is connected, all is good.She is using ADO.NET, there is no adodc control.

What are you using for your connection - OLEDbConnection, ODBCConnection, etc.
Also are you sure its just the connection thats slow or some loading of data through a OLEDbDataAdapter, OLEDbCommand, or ???

Can you post some relevant code?

What version are you running VB.NET 2002, 2003, or 2005 beta?

[wossname]

How much ram do you have? 256 is not enough to happily run XP in my experience.

I just upgraded to 640 and there have been huge efficiency gains all round.

But it does sound most likely to be a network bottleneck as mentioned above.