Think loosely, Pat. It would be convenient to cut and past and drag values across cells. (of course remembering to leave the keys alone) It would not be a good idea for general users; only for personal use.
I got it. Tell me if this is what you were looking for.
Just for interest sake - what is the reasoning behind the customer's request for this? Or did you just think it would be cool?
Have you tried converting the combobox, which you says works, to a listbox?
Select the good combo box in Design view. Go to the menu-item Format, Change To, List Box.
Solution for button to go invisible when/after it is clicked. See db example. The first part is to make the button invisible and an independent label visible. The second part makes the button visible and the label invisible. (That by clicking on the label). It works because in both click events...
To understand this, look at the table, tblName, the query, qryName and the module, called basChop. The module basChop contains two functions called ChopOne and ChopTwo, referred to by the query, qryName.
Guys. Do you realise Lac has very little experience in Access? You sound like Eskimo's talking in Eskimo about the higher mysticism of their religion would sound to you.
This code by Jacob Mathai found in the code repository and pasted below, seems not to work. The first line does something good. The table opens in Access. The second line opens the Tools menu item in the VBE, and the third line opens the References menu item under Tools.
To open a table in...
Works good! Thanks SJ.
I would like ctlPicker to keep its Value at the current date AUTOMATICALLY, and that is what I could not make work. I think because of the sequence of the events. The error message says that it is read-only.
In what Event (of the form or ctlPicker) could the line be...
How can I maintain the current date on this date-picker that Miles O aka SJMcAbney provided? The value line doesn't want to take anything but a date-constant. It has not worked from the VBE either.
Could SJMcAbney please help?
Nightwing,
Changes I made to your database to fix the problem of the doubling-up of investors.
1. Changed the group ID to Autonumber in the Group/Capital History Junction table. (because it is very awkward to have to think about an ID every time you create a new group.
2. Enforced referential...
If you go to design mode in the original database, you'll see a textbox with its property visible set to no hidden under the listbox. That is what it is referring to. You probably have not repeated that object in your test database.
Also make sure you have a reference set to Microsoft DAO 3.6...