Search results

This is an option but hiding columns will of course mean that the users won't be able to view them for reference.

Not that I know of I'm afraid!

Users shouldn't really enter details directly into a table. The way over this would be to design a form, disabling and locking the fields that you don't want them to touch, but enabling them to enter data into the fields you wish.

Do you actually mean columns or records? Columns, doesn't really appear to make a lot of sense, because the same ID will be recorded anyway. If you are opening different forms, then you can set different criteria within a query that feeds the combo box.

Thank you so much Kris - that works a treat. (I did try what you suggested Rich, but that didn't work).

11/07/03 in a, then nothing yet in b, c or d.

Well the error's stopped, but the value in the time field is: -907512:00 !!! :confused:

A little problem as a spin-off from this ... I'm now getting an overflow problem when I enter the dates because the first date is then trying to calculate with a null value. Does anyone know how to get over this please?

Excellent Fizz - you're wonderful. :D Col and I were both having a bash at it and neither of us were getting anywhere.

Thank you - This is one of the things I had tried, but unfortunately, it doesn't work either. I just tried Not IsDate too but that still returned #Error.

I have some code to sort out the datediff between times including dates. I'm calling it from a query. If the date and time fields are empty the time field I'm calculting gives #Error. The code is: Function TimeCount(a As Date, b As Date, c As Date, d As Date) Dim x As Integer, y As Integer...

All you need to do is in design view of your combobox, bring up the properties for that object. Find RowSource which will be near the top of the properties on the All tab. You'll have your SELECT ... etc in there. To the right of the box will be a button with "...". Click this and it will...

Oh that's excellent, works a treat - thanks Fizz. (The information is on another form - but the frmPatient displays the information that's just been deleted in a listbox, which is why it's being requeried).

Private Sub cmdDelete_Click() On Error GoTo Err_cmdDelete_Click Dim UserResponse As Integer DoCmd.SetWarnings False UserResponse = msgbox("Are you sure you wish to delete _ the current record?", vbYesNo, "Delete?") If UserResponse = vbYes Then DoCmd.DoMenuItem...

I have a form with a delete button, with the code the wizard put behind, but added code to ask for confirmation and select another form and requery it once deleted. I've used the same code before on a number of occasions, but on this particular form, when I say yes, it deletes the information...

My lips had better stay very sealed! :)

No you do this in the table design. In the properties section at the bottom, on the General tab, there's a Default Value space.

Blank records could be a problem I think if the default value is set to 0. You need to make sure they're set to Null.

I'm not a real expert on relationships, but this is because with referential integrity the records in the parent and child table must match. If there are any that don't match at all this will prevent you from setting RI in your relationships. If you've not got many records, one way is to bring...

No - it's on my hard drive, not the network and I use Win 2000. Just imported into a new db and it seems to have done the trick. Thank you very much.