Search results

Hi Jun, Not really thought of that one. You could make another table that has the name of the user in it, or an autonumber ID if you like that references to the user. and append the details each time rather than replace. I am a little out of my league on that one, any one else got ideas using...

Hi Jun90, Here is a sample of what you are more than likely after. Hope it helps. Remember to keep the list of users in the backend if you have a separated db. :)

You can also try playing with the command FilterOn and try setting to true false as well. in conjunction they work well.

Hi Rogue, try this Function SaveRecord() As Boolean On Error GoTo SaveRecord_Error Application.RunCommand acCmdSaveRecord SaveRecord = True SaveRecord_Exit: Exit Function SaveRecord_Error: SaveRecord = False End Functionit should take away the need to click save. EDIT: You...

You could try to 'hide' the form when the report opens and use the onopen in the report to then close the form. cdocmd.RunCommand acCmdWindowHide You can then use the report's OnOpen event to close form using docmd.close "FormName",acsave-Yes/No/Prompt-choose 1

Hey Coach, When the report is run next can you tell us what value is in the "Filter" field on the Form Properties page? To get this, after the report has opened go to desgin view on this and look at the second tab from the left second line down. If this info is not getting in there correctly...

It sounds to me like you have doubled up on your redundancies. By setting the required to true in the table and having the code trap to ensure the fields are filled you are getting two errors when something goes wrong. They are basically fighting each other. I much prefer having the validation...

Hi there, Afte getting a lot of help from this forum and now having built a resonably complex app for work. I figured it is my time to give back to the community. Here goes. For my Ex below you need a table named tblUserLog With the fields UserId (text)No Duplicates - saved me having an...