[dba-VB] OT: .NET - Data grid syncs to combo

John,

Less than a year ago, I decided to convert an access application to .Net. Within
one day, I had a working prototype in both VB.Net and C#.Net. It was extremely
easy. You are right in that the combo changes the data set which in turn affects
all controls linked to it. Just for kicks, I also bought Borland C++ and did the
same thing (within a day).

My conclusion is that all the major tools these days are offering click and
create applications. It's just a matter of picking the technology you think is
most marketable. I don't think you can go wrong in learning .Net. I'm still torn
as to what technology to pick (although the next version of .Net is coming out
in April and is just a $29 upgrade for previous .Net owners and includes the
capability to make Pocket PC.Net applications).

I'm very interested in discussing the techniques developers are using to convert
Access applications to .Net. 

Hoping to find intelligent useful discussion on .Net,

Scott Marcus 

-----Original Message-----
From: John W. Colby [mailto:jcolby at colbyconsulting.com]
Sent: Tuesday, February 25, 2003 8:32 PM
To: AccessD
Cc: AccessD - VBA
Subject: [dba-VB] OT: .NET - Data grid syncs to combo


I have moved my billing database BE to sql server, hooked up my existing
Access FE and continue to use that as I play with the data in .Net.

In the meantime, in VB.Net I created a bound form last night (or I think
it's bound anyway, not positive).  It was using an OLEConnection, which
tonight I switched to an SQL connection.  It's supposed to be faster.  The
form simply displays the state table (all fields) in a data grid.  You
really can't get much simpler than that, though I suppose for something like
a state table it would suffice.

I decided to try and figure out how to use a combo box to select a record in
the data grid.  Dragged and dropped a combo to the form, hooked the
datasource property to the same data source I was using for the form / data
grid.  Set the display member (the field displayed) to ST_Abrev (the 2 char
code), and the value member (the PK of the table) to ST_ID (the PK of the
table).  Opened the form, selected the state in the combo and the data grid
moved the record selector to that state.

Man was THAT easy!  So the combination of everything allows the combo to
just act as a record selector without all of the code required in Access.
Not knowing exactly what is happening, I have to assume that the combo
selecting something causes a record selector pointer in the data set object
to point somewhere.  Since the data grid is using the same data set object,
the data grid displays the newly selected record.

Just a guess of course.  This stuff is way over my head.

But so easy (if I just understood what I was doing).

Cool beans man!

John W. Colby
Colby Consulting
www.ColbyConsulting.com

----------------------------------------------------
Is email taking over your day?  Manage your time with eMailBoss.
Try it free!  http://www.eMailBoss.com


_______________________________________________
dba-VB mailing list
dba-VB at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-vb
http://www.databaseadvisors.com