Search results

Well, when you add a combobox in access, you can actually use a wizard to get the data you want. But yes for the second one you need a little knowledge of sql and vba.

Since you asked for a demo : http://www.access-programmers.co.uk/forums/attachment.php?attachmentid=64492&stc=1&d=1479292287 In the file you have a very limited database. And a form who show you how the combobox is working. When you select a country, it will show you all the visa's from that...

I would give you examples with fields of your database. But what do you already have as database ? Can we get a demo version of what you have ?

To populate a combobox you just need to put the query in the Row source and set the Row source type to table/query. A list box just show all the data. The combo box you see only the selected data. You can pick a new one with a dropdown menu. The listbox doesn't have a dropdown menu.

I guess you already have a table for the country and a table for the different categories. All you need is a intermediate table who store all the possible combinations. Then you can use that to make a query to populate your drop-down list.

Can you tell us how you determine the performance of a technician ? This will help if you need just a boolean or different table. Is the performance based on previous projects ?

I would just make a table with the project information. Then in the table of the technicians i add a field project_ID. So that i can pick one or more technicians for 1 project. That allows you to get projects that are not linked to any technicians and select the correct technician based on your...

Personally I'm not very fond of the check all the field one by one. What can happen is that if the user don't fill 2 field he will get 2 messages. First one will tell him to fill the first field. And second one will tell him to fill the second field. giving the user 1 message box with all the...

Well what you try to do is if field1 or field2 is empty, display a message then check if there was some kind of error. Since there are no errors, your code will just go to the gotorecord and start a new record. To fix that, you just need a Exit Sub right after the message box is displayed.

Did you already tried something ? Or do you want us to give you a working solution that meets all your requirements ? I would start by making a diagram with all the tables/enums. Once you have a basic layout of the database, check if you can normalize it. Once that is all done, you can start...

In that case your SQL is not correct. Do you have in the table tblTest an ID of the question ? If that is the case, then this would work beter : SELECT tblQuestions.ID, tblQuestions.Question, tblQuestions.Module FROM tblQuestions LEFT JOIN tblTest ON tblQuestions.ID=tblTest.lngQuestionID WHERE...

Maybe that a Left join will help you ? Example : SELECT tblQuestions.ID, tblQuestions.Question, tblQuestions.Module FROM tblQuestions LEFT JOIN tblTest ON tblQuestions.ID<>tblTest.lngQuestionID WHERE (((tblQuestions.Module)=[Forms]![frmTest]![cboModule]));

Minty, Don't you get a lot of nice to haves the first 3 months before a total overhaul ? Here it is sometimes even worse : After a few months of developing and starting to deploy the amazing access app some manager comes by and just say 'nope we are not going to use that. Stick to the endless...

Does shift + double click on the database work ? (It works with Office 2016.) Otherwise i guess microsoft wanted an even more exclusive way for their office 365. Edit : nevermind the shift+click... It doesn't open the database in exclusive mode. My bad :/

I guess you already have a form where you can enter the month and use that text-field in your query ? If so, you only need to add a new text-field. (Or maybe a drop-down to select the customer). And in the query add in the where statement "or ((tblPayement.Cust = txtCust.value) and...

Your code works fine. It's just that the difference between 7/2/2016 and 9/20/2016 is 2 month or 80 days. But maybe you want the difference in total. Like 0 year, 2 month and 18 days ?

Wait are there people who turn that OptionExplicit off ? Better keep it on and make the code clean and with no mistakes.

Here is an example. You need to get the date from the field first. Also you need to close the "IF" or else the code will not work.

Here is what I did : Made a query who will reset all the records in the table. You keep all the lines in that table but you can enter new dates again. The old dates are lost. So I don't know if you want to keep them or not.

Here is a thread about the same problem : http://www.access-programmers.co.uk/forums/showthread.php?t=70551 It can give you some ideas i hope.