Search results

Yep that did it. Just in case someone else is looking for a similar solution the code I have is as follows; Private Sub Form_KeyDown(KeyCode As Integer, Shift As Integer) On Error GoTo ErrorHandler 'Detect Down arrow If KeyCode = 40 Then DoCmd.GoToRecord...

Thanks, I'll give that a whirl after dinner.

My bad :o If keyascii = 38 Or 40 Then MsgBox "you pressed a key" End If is wrong and detects any key down, and the correct syntax of; If keyascii = 38 Or keyascii = 40 Then MsgBox "you pressed a key" End If fails too :banghead:

Thanks for that it's got me a little closer, but. If keyascii = 38 Or 40 Then MsgBox "you pressed a key" End If Works fine, but If keyascii = 38 Then MsgBox "you pressed a key" End If or If keyascii = 40 Then MsgBox "you pressed a key" End If...

Is it possible to detect the Up or Down arrow keys? I've tried using the following in the Form's Key Press event; MsgBox "You pressed the " & KeyAscii & " Key" Which returns the ASCII code for most other key but not the arrow keys :confused:

You could also consider distributing it under a Creative Commons license, which has more flexibility on the rights you retain and those that you give your end user.

pbouk, this has been reported previously, however there is nothing in the code that should be producing this type of behaviour. I suspect that it may be being caused by some system setting outside of Access. I have never been able to reproduce this error :confused: If you can post a copy of...

The sample here demonstrates one method. It has separate runs for each office and resets the run each day.

So long as the you have the basis for your calculation stored, the result (in most cases) does not need to be stored, as it can be reconstituted at any time you need to display the result. Read here for more. You might also want to read up on data normalisation and perhaps work through a...

Have a look at the sample here.

The field that is being derived from the combo and the calculated field, should in most cases not be saved. If one of the underlying values is changed this may not be reflected in your stored value. All you need to do is use a query or the same schema you are currently using to populate those...

Given that your Combo is able to populate an unbound text box using; =Comboboxname.Column(x) Why do you then need to store that value elsewhere :confused:

Welcome to the forum. You can populate an unbound text box by using the following as it's Control Source; =[ComboName].[column](X) Where X represents the column in the combo that hold the data you wish to display, remember that the columns in a Combo or listbox for that matter are numbered from...

Welcome to the forum. The After Update Event does not fire until you move to another record. So if you want the status to change as the records are altered you might try using each of the field's On Change event. Also you code should look like; If IsNull(Me.Date_Raised) then Me.Status =...

When ever you make a change to the front end and redistribute it you need to re-link it to the back end.

Dude; Please do not post the same question multiple times. It will not get you an answer any quicker :mad:

Dude; Please do not post the same question multiple times. It will not get you an answer any quicker :mad:

To expand a little on pbaldy's comment, most experienced developers will advise that; An Autonumber is for the database to maintain referential integrity. As the old saying goes, "An Autonumber is not for human consumption." so it should be irrelevant to the user what the autonumber is holding...

On the Design tab click the Add Existing Fields button.

Here's a sample that demonstrates how this might be done.