Shawn; Rob,
Thanks for your replies.
As usual, I came into work and am "in the thick of it."
I have a couple of basic questions that should not be hard to
answer. BTW: I will check out the links when I have time a little
later.
RE: VisData
First lets get one thing straight. I have VB 6.0 Enterprise
Edition, and MsOffice, and whatever that came with. I do not have
other applications to work with, and my company will NOT get me
anything else.
With that in mind, here's my questions...
With my previous problem regarding VisData, I am indeed able to
open my databases in ACCESS with no problem, the problem seems to be
isolated to VisData.
It dawned on me last night while I was worrying myself to sleep,
that I could use those fancy SQL statements in VisData to generate
the reports that I need on duplicate data, etc. Any reason why I
can't do this? Maybe I can use SQL statements in ACCESS? These are
things I have never considered or been educated on. Currently it
takes a few hours for my programs to do the dupe checking and what-
not. If I could take advantage of SQL, then that would be great.
For doing "on-the-fly" tasks like the dupe checking, etc. I wouldn't
have to take the time to write a program to do it if I could just
fire off a query in Access or VisData.
Also, I remember when I installed VB 6.0 there was a SQL server,
or SQL something-or-other that did not install because my computer
name had a "-" in it. They finally changed the computer name (yes,
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.), and if anyone can recall what that SQL-related
software was that came with Enterprise Edition, and if it will help
me, then I can go convince the powers that be to give me the [EMAIL PROTECTED]
disks so I can re-install it.
Also, if I want to switch to ADO, I simply have to use the ADO
6.0 reference I found in VB 6.0? And, I need clarity here... ADO
does NOT allow for the creating of DB from code? This is an absolute
must for what I do and why I still use DAO in applications that
create databases. For dealing with databases that are already
existant, I acknowledge the necessity of moving to ADO.
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?
Thank you all.
[C]
'// =======================================================
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/
