Hi Chris,
> Thanks for your replies.
:)
> As usual, I came into work and am "in the thick of it."
We were all there once, that's why we 'consult' now. We like this
part:
> not only do they not provide me with appropriate tools to do my
> job, but also I have to depend on a computer guy who I have never
> met, and comes in at his whim to do things that have to do with
> network administration, etc.)
...Because, as consultants, we get to demand the client provide
certain things in order to accomplish what they need. If they choose
to ignore us then we just buy it and bill them for it (+20%
handling).
> Maybe I can use SQL statements in ACCESS?
Yep, open access and click on the 'queries' tab on the left side.
Then use a query wizard, but don't get too close to the wizards -
they create ugly SQL. The "SQL" button at the top (in a query view)
will get you to the actual SQL of the query, and the little grid
button will let you preview the results.
> Also, I remember when I installed VB 6.0 there was a SQL
> server, or SQL something-or-other...
SQL Server Enterprise Manager. It won't do you any good in your
situation. It's designed for SQL Server, and you're using Access.
> Also, if I want to switch to ADO, I simply have to use the ADO
> 6.0 reference I found in VB 6.0?
Pretty much.
> And, I need clarity here... ADO does NOT allow for the creating
> of DB from code?
It *does*. Even if it did not (though it DOES) you could use BOTH
ADO and DAO in your references, you just need to be a bit more
explicit when declaring objects.
> And, I am still a little unclear, if I move the fields around
> in a database and divide them up into multiple tables, how
> will that affect the size or speed of the database?
Negligible. The primary concern isn't speed, it's function. A few
seconds lost in total over millions of operations won't be noticed.
Oh, and I ought to make sure you're aware before you get into
screwing around with the db design, in table/field names:
# don't use spaces
# don't use underscores (_)
# don't use control characters (',`,[,],(,),-,+,=,&,*,%,$,...)
# don't use anything but the simple alphabet and numbers
Some database layers make it more difficult to work with if you have
these weird characters in table and field names. You should also try
to avoid using a table name as a field name anywhere. With 140
fields I recognize the difficulty in naming, so I just want to warn
you in advance. :)
Maybe I'll release my MDB-to-ASP code. It's got some pretty sweet
shtuff in it for generating interfaces on the fly (and no - it's not
limited to only ASP - it can be (and has been) used in vb exe's and
components, too). Until you get your head wrapped around the ADO
objects I'm scared to point you to it, though. It does some things
in a couple hundred lines that might scare you away from ADO
altogether. :/
Regards,
Shawn K. Hall
http://12PointDesign.com/
http://ReliableAnswers.com/
'// ========================================================
The best time to miss a train is at a crossing.
'// =======================================================
Rules : http://ReliableAnswers.com/List/Rules.asp
Home : http://groups.yahoo.com/group/vbHelp/
=======================================================
Post : [email protected]
Join : [EMAIL PROTECTED]
Leave : [EMAIL PROTECTED]
'// =======================================================
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/vbhelp/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
