|
-
Aug 1st, 2000, 03:56 AM
#1
Thread Starter
New Member
I've just upgraded to VB 6 SP3 from VB 4.
I have a VB4 4 project which works fine reading and writing to various databases, using DAO. Now I want to add a new form to access a list of values from a field in a different table to populate a data combo box. Everything is OK until I try to change the RowSource property of the combo box, at which point the properties disappear. I've got a ADO control connected to my database OK and the combo box will display one value, but it won't list the values.
Any suggestions?
-
Aug 1st, 2000, 07:30 AM
#2
Lively Member
Are you using two ADO controls for your DataCombo? You need one for the DataSource and one for the RowSource. Make sure you have the following properties set.
DataSource, DataField, RowSource, ListField, and BoundColumn. If you need more help with this, post information about your db. (Field names)
Dr_Evil
Senior Programmer
VS6 EE
VS.NET EA
-
Aug 1st, 2000, 08:27 AM
#3
Thread Starter
New Member
I've got two ADO controls, but as soon as I try to click on the RowSource property of the Data Combo all the property information disappears. I can't enter anything into the RowSource at all, everything else is filled in DataSource, DataField etc. On other combos on other forms that were created in VB4 using the DAO control they work fine, but if I try to change the RowSource the same happens.
-
Aug 1st, 2000, 08:56 AM
#4
Lively Member
I had the same problem with the record source...one day it was working the next it wasn't...after investigation I found the problem...
I had recently started planing with Crystal and had inserted two views in two separate forms with the same name,
once I deleted one of them I could see all my properties...
Not sure if this will help
Gerard
-
Aug 2nd, 2000, 05:34 AM
#5
Thread Starter
New Member
To solve the problem I created the form in a new project and then added the file into the VB4 project.
I still can't change the RowSource but I managed to set the Datacombo boxes up correctly in the new project.
I suspect that there is a problem with the project because it was a VB4 project originally.
Not the best solution but it worked!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|