Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Beginning database questions (Access & VB)

Status
Not open for further replies.

Catrina

Programmer
Feb 11, 2000
70
US
I am currently converting a DOS payroll application to windows. The database we currently use is not compatible with the new VB application. I am just a beginning programmer, and I'm now to the part where I need to deal with the database questions. I have taken a class on Access (just how to use it, by its self), so I am most comfortable with it, but willing to take suggestions. Here are the questions:<br><br>1. Will I be creating an empty database using Access (fields defined), then include it in the package and deployment with the application?<br><br>2. My boss wants to lump several fields together for security reasons (one huge long number, so no one can tell rates, SS# etc.). Will I be able to do Mid$ on the database fields to extract just the data I need? (THIS IS THE MOST IMPORTANT QUESTION)<br><br>3. The book I am currently (just started) using to learn about database programming is binding text boxes to database fields using the data control. Even if I wanted to do this, I couldn't because of the request for the lumped together fields. I have glanced ahead, and wondered if DAO or ADO is how I will be &quot;binding&quot; the input. Can someone explain a little about DAO or ADO, is it a language, a control, just a general idea, so I'm a little less confused.<br><br>I'm sure I will have more questions, so any extra input would be greatly appreciated.<br>Thanks in advance for any help.<br><br>Catrina
 
ADO works best in my opinion, DAO is almost Obselete as mentioned in most Microsoft MSDN, check the FAQ for a small example of working with ADO. depending on how your application works that #2 might not be nesasary. <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href= </a><br>Experienced in : C++(both VC++ and Borland),VB1(dos) thru VB6, Delphi 3 pro, HTML, Visual InterDev 6(ASP(WebProgramming/Vbscript)<br>
 
I think your boss has the wrong idea with lumping fields together.&nbsp;&nbsp;Sounds like the thing he is really after is a secure environment.&nbsp;&nbsp;Access can provide that environment, but it is a bit ugly.&nbsp;&nbsp;How many users are going to be using this payroll system?&nbsp;&nbsp;I understand that Access does not do well at supporting large numbers of users (like more than 6 or 12).&nbsp;&nbsp;You may want to consider a more robust database like SQL Server.&nbsp;&nbsp;I would really urge you to not lump your fields together.&nbsp;&nbsp;It will reduce performance, make support a night mare, etc.&nbsp;&nbsp;I am currently assigned to a PeopleSoft payroll project.&nbsp;&nbsp;If you were to lump the fields together in those thousands of tables, it would be a complete nightmare.&nbsp;&nbsp;Just implement some good security.<br><br>I was part of a development team that wrote a large application in VB3 using bound controls.&nbsp;&nbsp;The performance was lousy.&nbsp;&nbsp;I don't know how that may have improved over the last 3 versions, but my office has outlawed the use of bound controls.&nbsp;&nbsp;Everything uses either ADO or direct calls to the ODBC API (it's still faster than ADO).&nbsp;&nbsp;<br><br>
 
Thanks for the replies. Each company using our service will have its own database, the transactions are then transmitted to our main frame for processing, so the databases are not going to be large or multi-user. About the security, I know Access can encrypt the database, but can't someone decode it with Access also?<br><br>I'm not planning on binding controls, I just haven't gotten past that part in the training book I am using. <br><br>My boss is an old time self taught programmer (DOS only, that is why I am learning VB and not him (he hates change)), who is pretty set in his ways. Security is of major importance to him, so I'm pretty much at his mercy where the lumped fields are concerned.&nbsp;&nbsp;Unless it is just impossible, I'm going to do it his way. Maybe after the first version, I can do it differently and convert him.
 
Your boss should realize that if someone is motivated and savvy enough to decrypt your database, they're also probably motivated and savvy enough to parse your lumped field and comprehend your data.<br>Lumping fields together violates one of the fundamental concepts of database design and you will definately regret it (probably sooner rather than later).
 
Jerrycurl is right, if you want to lump fields together, you're better off with a text file, and a program to interface it with, the goal to better database managment is to normalize the data, also depending on your enviroment and platform you dont have to worry about how to design your DB, as long as you design the interface correctly. <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href= </a><br>Experienced in : C++(both VC++ and Borland),VB1(dos) thru VB6, Delphi 3 pro, HTML, Visual InterDev 6(ASP(WebProgramming/Vbscript)<br>
 
The only good reason to lump fields together would be to create a unique record identifier (like last name and the last 4 digits of the telephone number).&nbsp;&nbsp;You might want to think in terms of normalization by creating related tables based on one-to-many relationships.&nbsp;&nbsp;The lumping may create data anomolies, thus defeating the utility of a relational DBMS.
 
I think that you misinterpreted my thoughts on security.&nbsp;&nbsp;I wouldn't try encrypting the database, I would implement the typical userid/password type security.&nbsp;&nbsp;Even from a differenct access database, you would need to provide that userid and password.&nbsp;&nbsp;If you're still concerned about the encrypting, then I would implement both.<br><br>As for your boss, my dad was an old self-taught basic programmer on a WANG system.&nbsp;&nbsp;I like my dad a lot, but you couldn't pay me to either support his code or write a system using the methodologies that he used.&nbsp;&nbsp;You need to find a politically correct way to tell your boss to manage the resources and let you manage the technical aspects of the project.&nbsp;&nbsp;If he is already influencing your technical design when he does not have the expertise to backup his decisions, then you are wandering into a very unpleasent project.&nbsp;&nbsp;Best of luck to you!<br><br>Rekclaw
 
if this is being done with a Access database, that is on the server, and the application is on the server (or the application communicates with a program on the server) apply a general Username/Password should be fine, since it cannot be accessed off the network, only by one of the local programs (unless its a SQL server) <p>Karl<br><a href=mailto:kb244@kb244.8m.com>kb244@kb244.8m.com</a><br><a href= </a><br>Experienced in : C++(both VC++ and Borland),VB1(dos) thru VB6, Delphi 3 pro, HTML, Visual InterDev 6(ASP(WebProgramming/Vbscript)<br>
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top