Date & Time Stamp

[Guest]

I have a field in all of my forms for notes. Is there a command that I run that will autofill the date and time everytime I select it. For example, press button today, today's date entered, then I enter notes. Press button tomorrow, date is enter below that note ect.... Just looking for some tips. Thanks........

 

[Allen Browne]

If the date of the notes is important, would you consider creating a related
table to hold the notes?

That way you can use an actual date/time field (and a "user" field if
desired), and easily sort/filter the notes as desired.

The alternative to add today's date to the end of the memo field on a new
line would be:

Private Sub cmdAddNote_Click()
With Me.[NameOfYourMemoFieldHere]
.Value = .Value + vbCrLf & Date
End With
End Sub

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

I have a field in all of my forms for notes. Is there a command that I

run that will autofill the date and time everytime I select it. For
example, press button today, today's date entered, then I enter notes.
Press button tomorrow, date is enter below that note ect.... Just looking
for some tips. Thanks........

 

[Guest]

I don't know if this is the best place to ask this, but it sounds good.....
We are using Office 2000, some Pro, some SBE. For those with SBE we use the Access Runtime to enable them to enter info in forms. We have some auto filled date fields that do not work on all workstations. It appears the XP machines fill the field correctly, but the Win 2000 machines do not. Any knowledge of this anyone ?

 

[StCyrM]

Hi Joel

Sounds like a References problem to me.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

Best regards
Maurice St-Cyr

 

[Douglas J. Steele]

While your analysis of the problem is likely correct, Maurice, unfortunately
your solution isn't possible with the runtime version, as you can't set
references using the runtime.

For that situation, it's necessary to open the database on a machine with
the full version of Access, and determine the location of each referenced
file, The following code may help:

Sub ListReferences()
Dim refCurr As Reference

For Each refCurr In Application.References
Debug.Print refCurr.Name & ": " & refCurr.FullPath
Next

End Sub

Once you know each referenced file, determine the exact version of each. One
way to do this is to select each file using File Explorer, right-click.
select Properties and find the Version information.

Once you have all that information, make sure that the exact same version of
each file exists in the exact same location on each workstation.