Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
-
Calculating no. of days between dates
Off the top of my head, I think the #name error is because Access can't find one of field names. Try modifying the syntax 'missingling' supplied, replacing the tablenames and fieldnames as appropriate. ElapsedDays= DateDiff("y", [tablename]![CurrentDate ], [tablename]![NextServiceDate]) tct1954- tct1954
- Post #7
- Forum: Microsoft: Access Forms
-
Load form with only one record so saves only once
Belovedcej, I think using a bound form and controls would be easier and less coding would be required. Setting up a form, binding to a recordsource, navigating through the recordsource one record at a time, adding, deleting, updating and saving records is all rather simple. Easier to maintain...- tct1954
- Post #8
- Forum: Microsoft: Access Project (ADP)
-
Load form with only one record so saves only once
belovedcej, The UK Professor's slides is what I had in mind. However I think his code is going to give you errors. At least I get them [bigsmile]. Substitute the bang -!- for the periods when referring to fieldnames. Also, I've never used the syntax 'Field("fieldname"). Check this snippet...- tct1954
- Post #6
- Forum: Microsoft: Access Project (ADP)
-
Load form with only one record so saves only once
belovedcej, Are the fields on the form bound to the view? If so, you would have to unbind each field and "populate" the fields with code. tct1954- tct1954
- Post #3
- Forum: Microsoft: Access Project (ADP)
