I have Office Professional 2013.

I have it installed on an Asus Laptop running Windows 8.1.

Also OP 2010 on Windows 7.

I open 99% of my files through "File Explorer" as I have several thousand (files) sorted into numerous sub-folders.

Whenever I open an Access file to check some details and then close it WITHOUT MAKING CHANGES "File Explorer" shows that Access has automatically changed the "Date Modified" to the most recent date and time that I open and then close the file.

This is despite the fact that the last time I may have made a change whether in design or data entry to the file was 2 - 5 years earlier.

This is unbelievably annoying.

Please have the Microsoft programming department make a modification so that the "Modified Date" policy is the same for all Office Professional programs and will only be updated if changes to design or data entries have been made. Please apply this to Access 2010, 2013 and 2016. I like many people have several computers with different Office Pro versions.

I sometimes have several hundred to a thousand files of very similar names and use the Date Modified to sort or get information from them.

Why is it that if you open a MS Word 2013 file and close it without changes there is NO date change to "Date Modified" when you view the file in File Explorer?

or

If you open a MS Excel 2013 file and close it without changes there is NO date change to "Date Modified" when you view the file in File Explorer?

Sometime if you make a change in Excel or Word and then decide against it both programs first ask if you want to update changes and if you say no Word and Excel store the original dates and DO NOT CHANGE THE FILE DATE TO THE MOST CURRENT DATE OF OPENING.

Yet if you open MS Access 2013 and close it without changes there is ALWAYS a date change to "Date Modified" when you view the file in File Explorer?

If a solution currently exists to stop the date from changing when there have not been any changes then I would appreciate knowing how to stop it.

I have gone through the Microsoft Community and other sources and wasted several days to solve this problem but no-one seems to have an answer. In the process of searching I have found many other people frustrated with the date change problem .

Why is there no continuity in Microsofts multiple program designs with respect to this problem.

I have been buying Office Pro & access when it was a separate program for as long as they existed and have always had this problem. I never had this problem when I also used Paradox.

Thank you

I was looking for Microsoft Access assistance for an issue I'm having with importing date data from a .csv file. I'd like to import as Date, Short Date. The only option I'm seeing is Date with Time, which does not work when importing my date data. Using the date with time option actually deletes all of the dates that I'm trying to import. If I select text, I need to go in and change all date fields after each import to be date, short date formatted. Help please! Am I missing something? Can this be fixed, or will I need to first change my file to Excel in order to import the date correctly?

In 64-bit VBA hosts, inlined member calls on user objects don't work like on 32-bit VBA hosts.

Given a UserClass with a getter/setter and a Class_Terminate handler (even it is empty).
And in a TestModule a factory procedure returning an instance of this class and also setting the setter.

When I now use this procedure and inline check the value of the getter like in the following sample, it results in a different behaviour compared to 32-bit VBA:

If CreateUserClass(True).TheValue Then

Please take a look in the attached text file for a complete sample:

UserClass.cls:

Private mValue As Boolean

Private Sub Class_Terminate()
'
End Sub

Public Property Get TheValue() As Boolean

TheValue = mValue

End Property

Public Property Let TheValue(ByVal value As Boolean)

mValue = value

End Property

TestModule.bas:

Public Function CreateUserClass(ByVal value As Boolean) As UserClass

Set CreateUserClass = New UserClass

CreateUserClass.TheValue = value

End Function

Public Sub ShortTest()

Const VALUE_TO_TEST As Boolean = True


Debug.Print "Value to check: " & VALUE_TO_TEST

If Not CreateUserClass(VALUE_TO_TEST).TheValue Then

    Debug.Print "This is wrong"

Else

    Debug.Print "This would be correct"

End If

End Sub

Old versions of office allowed users to install on any hard drive they wanted. The current office 2016 consumes up valuable hard drive space for the Operating System. Allow the user to decide where they want it installed. To make it easy have a express or custom option for installation. I have seen many companies use this option it allows easy installation for those who are less tech savvy and those who have experience to customize their installation. I use Visual Studio 2017 and it allows an installation option. THIS IS A MUST most people have small hard drives for the OS especially SSD which are about 140 GB which is OK for an OS itself.