Re: Access 2003 and SQL Server 2000 record locks (long)
- From: Rich P <rpng123@xxxxxxx>
- Date: 29 Nov 2007 21:11:02 GMT
Hi Jim,
I use the standard datagridview that comes with VS2005. Here is the
catch though, VS2005 works best with a 2.8 gig processor or higher and
at least 2 gigs of memory. I have had hardware issues at my place for
people that are still using 1.8 gig processors and 1 gig of mem. The
memory at 1 gig isn't actually that bad (if they aren't loading hundreds
of thousands of records), but the 1.8 gig processor does hurt a little
bit. But if you are going to load 200,000 records into a table -
remember that in .Net it is all in memory. So 2 gigs definitley better
than 1 gig.
Net is fairly resource intensive, but if your hardware has enough
horsepower, you won't notice it (big IF -- I know).
Rich
*** Sent via Developersdex http://www.developersdex.com ***
.
- Follow-Ups:
- Re: Access 2003 and SQL Server 2000 record locks (long)
- From: jsacrey
- Re: Access 2003 and SQL Server 2000 record locks (long)
- References:
- Re: Access 2003 and SQL Server 2000 record locks (long)
- From: jsacrey
- Re: Access 2003 and SQL Server 2000 record locks (long)
- Prev by Date: Assigning A Value To A Field In A One Row Table With VBA
- Next by Date: Re: Access 2003 and SQL Server 2000 record locks (long)
- Previous by thread: Re: Access 2003 and SQL Server 2000 record locks (long)
- Next by thread: Re: Access 2003 and SQL Server 2000 record locks (long)
- Index(es):
Relevant Pages
|