Comments by Gustav Brock (Top 30 by date)

What is the error? And what value do you assign it? And is that a valid ID?

From within the form, you can do it anywhere. Above, I assumed a textbox, now the single code-line should read:

Me!YourCombobox.Value = username1

If your combobox is bound to the first field, the ID, and username1 holds an ID (from the line: username1 = Me.tb_ID.Value), you should be able to assign this ID to the combobox and it will display the name.
To "reach" another object" from another table, adjust the query to have a JOIN to that table.

It looks like your field is a combobox bound to the field. Then you (typically) must supply the ID of the username, but - from your code - that already seems to be the case and what is stored in username1.

Try a little debugging and check that you manually can enter the value in the table.

I can see on SO, that you don't have a field but a label. For a label, assign the global to the Caption property of the label.

OK. But you seem not to assign username1 to anything.

It has. Perhaps you should reveal your code.

Not related to Microsoft Access.

"I had created the project as a Web Application instead of Web Site."

Why didn't I think of that? It took me two days to resolve this simple mistake. Thanks!

The week cannot both start and end on the same weekday. It must start Thursday or end Tuesday. Except, of course but unlikely, that the end/start point is Noon, Wednesday. Please clarify.

You would also have to double-check the value you try to update with:

rs(ctl.Tag).Value = ctl.Value

I don't disagree with you, but sometimes a simple question needs a simple answer.
Just curious, but how would you inject a DateTimePicker control? Or rather: make it return anything but a DateTime value?

Again?
Everyone can toss a link, and the questioneer certainly has an idea, only just misses the final detail.

While your comment is right, it is not an answer.

The only reason for your trouble was "Password" which is a reserved word, thus needs brackets, [Password] which, in general, are not needed.

Reason for my vote of 5 \n Neat!

That function believes all years contain 365 days which is not the case for leap years.

This will never work - a birthdate is always back in time.

Yes, what is the question?

Yes:
Order By IIf(something = True, 1, 2)
Or nested:
Order By IIf(something = True, 1, IIf(Somethingelse = True, 2, 3))

You are welcome. Have a nice weekend!

Indeed. Most reports in Northwind.NET are controlled by parameters.

That would be:

SELECT
ID, [Name]
FROM
tblYourTable
ORDER BY
([ID]-2) \ 3, ID DESC;

Adjust the subtrahend between 0 and 2 to control the sequence.

I don't know why Dave believes DAO has been dead for 15 years? It is alive and well and has been and still is the preferred method in Access and VBA from version 1.0 through the upcoming 2016 (excluding one version many years ago).

That corrected, I haven't used DAO from within C#, but a little searching reveals this link which should get you going:

http://www.codeproject.com/Questions/208386/using-DAO-to-retrieve-access-data-in-Csharp

This link is in C++ (and also falsely mentions the death of DAO) - still it could give you some ideas:

http://www.codeproject.com/Articles/25209/Using-Data-Access-Objects-DAO-with-WTL

Thanks. You may mark with a five-star. Note please, that I changed acSaveYes to acSaveNo which makes more sense as no changes are done.