We have a MS Access application that has a problem taking a date, there are 6 values that associate with a date on a local system and connect to odbc. This is a application that builds reports but when it runs it creates errors at one point. Sometimes it seems like 5 of the dates that are set on the local system that runs the program accept the local systems date. When we got the app the field mid date end was programmed to auto enter a date in November 2012 but the rest of the dates in the main form take system dates. When you run the program you get an error about an invalid setting. If YOU actually ran it you would build off of tables that go into the millions of rows, but there is an error in the code surrounding the time parameters...DATE we believe. If you run it with the field explained above with a manually created date that is auto inserted upon the run..it may work. We need to make it a date from the beginning of the month last month to the middle of the same month so that it doesn't make almost a million rows and most importantly doesn't crash after it has been running through the various tables it analyzes for the 25-40 minutes it takes to run. But if you don't format some of the date fields right the thing would run forever then crash. We think it has to do with the date being inputted in one field.
Anyhow we need a PROFESSIONAL that can quickly asses this problem and find a solution.
We can send the database which is in MS access 97..yes it is old....tell us what u think and if you can solve it...if you can we would be happy to speak..there is a potential for way more work as we have a bunch of these old applications