Charlotte Foust
cfoust at infostatsystems.com
Fri Jul 22 10:47:48 CDT 2005
I use two and put the solution explorer, properties window, etc. on the second. A couple of other developer stretch the interface across the two monitors, which drives me nuts when I try to find anything on their screen! I admit that it is handy for VS.Net, but I think dual monitors are useless for any other purpose except testing. Charlotte Foust -----Original Message----- From: Arthur Fuller [mailto:artful at rogers.com] Sent: Friday, July 22, 2005 8:39 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] VBExpress videos William (and any others interested)... If your box can support a pair of monitors I strongly suggest that you go that way. Then you can really begin to enjoy the UI of .NET, because you can drag all the toolbars etc. to the second monitor and have a nice clean surface to work on. This changes everything! (Incidentally, the same applies to Dreamweaver MX.) Once you go to using two monitors, it is very difficult to go back. Arthur -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Hindman Sent: July 22, 2005 2:09 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] VBExpress videos ..thanks JC, I'll dl the videos and have a look then ...tap dancing around VB.net whenever I'm bored with everything else going on ...the VB name is similar but the ide keeps throwing me for a loop and nothing ports cleanly, at least for me ...but I admit to getting old :) -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com