2001-09-05, 02:34 #1
- Join Date
- Jan 2001
- Thanked 0 Times in 0 Posts
Form to enter data into an mdb (Access, VB6, W2000)
I have 3 tables; tblProject (ProjectID*, ProjDesc, ClientID*, JobNo*), tblClient (ClientID*, ClientName), and tblJobNo (JobNo*) in my access mdb. I used VB6's wizard to make a form. I can scroll thru my projects and view them fine. When i hit the "add" key i can add new projects but i can't view the clients and jobno's that are already entered in my mdb tables. How can i make these a dropdown list box that will show what is already in my tblClient and tblJobNo when i hit the "add" button?
Also, when I add new projects that have new clients and new jobnos will all 3 tables be updated?
I can do this easily in Access but none of my users have access and the run-time version is too cumbersome to give them. I would like to write a VB application instead but what is ez in Access, i don't know how to transfer to Visual Basic code. Can someone please give me a start in the right direction. I've looked in northwind.mdb but i can't find what i need. If someone has a sample vb example that would help me greatly.
Thanks very much.
Subscribe to our Windows Secrets Newsletter - It's Free!
Get our unique weekly Newsletter with tips and techniques, how to's and critical updates on Windows 7, Windows 8, Windows XP, Firefox, Internet Explorer, Google, etc. Join our 480,000 subscribers!
+ Get this BONUS — free!
Get the most of Excel! Learn about new features, basics of creating a new spreadsheet and using the infamous Ribbon in the first chapter of Excel 2013: The Missing Manual - Subscribe and download Chapter 1 for free!
2001-09-05, 13:58 #2
- Join Date
- Dec 2000
- Sacramento, California, USA
- Thanked 1 Time in 1 Post
Re: Form to enter data into an mdb (Access, VB6, W2000)
I would *not* recommend that you try to learn VB while building a database front end. The Access runtime is no more cumbersome than the VB runtime, you just don't see VB people admit that. Instead the focus is on the "little" executable you can create with VB instead of the large runtime that supports it.
If you insist on doing it with VB, you're going to have to learn to use the ADODataControl to give you anything that even comes within spitting distance of the built-in functionality in Access forms and controls. And you'll still need to use the Packaging and Deployment wizard to create setups for the other machines just to be sure that all the dlls and object libraries used are the same versions on all the machines.Charlotte