M
Masahiro Ito
I am new to database programming, and would like to follow the preferred
programming methods when possible...
I have large databases, in a small 'always connected' environment. I have
been pulling large tables, and creating filters with some checkboxes etc..,
which create dataviews. Couple of questions:
1. Is there an easier way to create the filters than a bunch of IF THEN's
to create the filter string? (ie: if first filter add "(", if last add
")", if not first or last add " or ")...
2. Can I use the Compute command on dataviews?
3. I have been creating some classes to help with the 'logic' of analysis
on some of the data. It appears to me that developers choose between
either using the DataAdapters, Datasets and bound data direct from the
database for their forms, or they create class objects, and bind the
classes to the datasources. It would appear that classes would be the
safest, but more complex route. The VB books that I have spend good energy
on classes, and then good energy on ADO, but always seem to separate ADO
from classes (ie: run through all the standard dataadapter/dataset bound
directly to the forms components). I am currently enjoying the Deitel
VB.NET book, which I highly recommend to beginning programmers - but it
will take me some time to get through it.
Looking forward to any comments.
Masa
programming methods when possible...
I have large databases, in a small 'always connected' environment. I have
been pulling large tables, and creating filters with some checkboxes etc..,
which create dataviews. Couple of questions:
1. Is there an easier way to create the filters than a bunch of IF THEN's
to create the filter string? (ie: if first filter add "(", if last add
")", if not first or last add " or ")...
2. Can I use the Compute command on dataviews?
3. I have been creating some classes to help with the 'logic' of analysis
on some of the data. It appears to me that developers choose between
either using the DataAdapters, Datasets and bound data direct from the
database for their forms, or they create class objects, and bind the
classes to the datasources. It would appear that classes would be the
safest, but more complex route. The VB books that I have spend good energy
on classes, and then good energy on ADO, but always seem to separate ADO
from classes (ie: run through all the standard dataadapter/dataset bound
directly to the forms components). I am currently enjoying the Deitel
VB.NET book, which I highly recommend to beginning programmers - but it
will take me some time to get through it.
Looking forward to any comments.
Masa