Saving Dates in a Table

[bo16tx]

Not worried about slamming, believe in open and honest communications. Best way to find solutions.

This database was put together many years ago from an extreme mismatch of data source, e.g., Lotus 121, Viscalc, dbase, Foxbase, etc. We hired a contractor that supposedly knew Access to help us put together an useable database. What you see is what we got! I'm an User not a programmer, so several of the items about, I don't understand. The comment about every code module. I've never DEBUG'd a database. So when it said novice, that might be an overstatement. I do know, if I start changing names within Tables, that's going to brake or things. Just not sure I'm smart enough to fix. This systems gets used on nearly a dayly basis, so taking it off line for more than a day or 2 can cause havoc. I saw John G's comment below about spaces in Date field Names. Could start there. I got this error when running DEBUG, (ActiveXCtl83.Visible = True) but have no clue as to what it means? Not a VBA person either.

[JoeM]

The field you are entering data into is called Manifest Date. Apparently Access doesn't like the word "Date" (preceded by a space) in the field name. I changed the field name to Manifest_Date (no space) and voila! - it worked. I suspect any field like [xxx Date] with a space will have the same problem - I found the same thing in another table.

I am not so sure that the issue is the word "Date" preceded by a space, and not just the space, in and of itself.

Best programming practices say to never use any spaces in the names of fields or objects (usually use underscores, as you have done).

[John_G]

Joe -

I am not so sure that the issue is the word "Date" preceded by a space, and not just the space, in and of itself.

I think this issue is in the newer versions of Access. I have 2016, and I was able to replicate the problem in one of my own databases. In my opinion, this should be considered an MS Access bug, since spaces in field names are allowed (even though it is bad practice) and cause no issues if one is consistent in using the [...] where required. But, you are correct - best not to use spaces. I do (or did) it all the time, and I'm fixing things as I go.

[JoeM]

I think this issue is in the newer versions of Access. I have 2016, and I was able to replicate the problem in one of my own databases.

I am curious...

If you change it to "Manifest Dat", does it work?
If it does, then it seems to support your thought that it doesn't like " Date".
But if it does not, then that would seem to suggest that the issue is really with the space and probably doesn't have anything to do with the word " Date" (since " Dat" has the same issue).

[John_G]

Curiouser and curiouser.

I am no longer able to replicate your issue, either in your database or mine. Dates are saved fine, even after closing and reopening the database. Now, in the time when you first reported the problem (and I confirmed it) and today, MS applied a Windows 10 and Office update (but I dont think MS Access itself as well). So, before the update the dates didn't work, now they do.

Coincidence? I doubt it.

What version of Windows 10 are you running?