There is no object in the control - ms-access-2016

I upgraded an Access 2010 project to Access 2016 64-bit. In the process of testing for incompatibilities I ran into this error while the code attempts to assign a date value to a control. The problem line in question is:
Me.axDate = CStr(Int(CDate(Me.OpenArgs)))
The value of Me.OpenArgs = "Jan/06/2007 10:00:00 AM"
Any ideas on why this does not work in Access 2016 would be greatly appreciated. John


Python 3.5 Dropbox API modified date doesn't update

I'm writing a script in python3.5 that needs to check if the file on dropbox is
newer then a local file. If the file is newer, it needs to download the file.
The problem I'm having is that the date on the server doesn't seem to update. Is it possible that it only update on certain times?
code snippet:
def check_if_needed(dbx):
server_date = dbx.files_get_metadata('/').server_modified
version_epoch = os.path.getmtime('versie.txt')
version_date = datetime.datetime.fromtimestamp(version_epoch)
print (server_date)
print (version_date)
if (version_date < server_date):
return True
return False
2016-10-10 13:05:35
2016-10-10 15:04:25.861405
what it should be:
2016-10-10 15:04:25.861405
So it returns False, while it has to be True.
I have updated the file on dropbox a couple of times, but it stil doesn't update. I have also looked on the internet but I couldn't find anything. Also I doesn't use the dropbox client, but directly in the browser, and yes I'm updating the file in the Apps folder created by dropbox ;)
If more information is needed, let me know!
Anyone able to help me?
Thanks in advance!
The problem was the difference between timezones. I'm in GMT +2 while dropbox is GMT +0. So I chanced this line
version_date = datetime.datetime.fromtimestamp(version_epoch) - datetime.timedelta(hours=2)
Now it works perfectly.

Setting the xField to a mysql date on ColumnChart?

I'm using Flash Builder 4.5 and trying to accomplish a charts dashboard task and everything works except one thing: the date when pulled from the MySQL, I can't order the columns by it. i don't care (even prefer) to make the dates like 01.06.2011 or 01/06/2011 i just need to do this somehow.
So this is what I'm doing on the service file:
$row->date = new DateTime($row->date);
When testing the operation i can see its pulling the date in this format:
Tue Jun 14 01:00:00 EEST 2011

QuickBooks SDK PurchaseOrderAdd.RefNumber.SetValue()

On December 4, 2013, the Quickbooks Pro 2013 SDK appears to have changed its behavior.
I have issued this command for years:
SalesOrderValue = returned Sales Order Reference Value from creating a Sales Order
Quickbooks is no longer respecting this command. The created Purchase Order Reference Number is now the next consecutive Sales order Number, not the number that I tell it to use.
I have rebuilt the Quickbooks Data File. It did not help (hoping it was a bad index)
Any idea on what has happened? More importantly, is there is a fix to restore this functionality?
Completely ripping off 'user3150303' else but we installed SDK 13.0, and changed version number to 12 and it worked.
I had the same issue, only using QBFC. I fixed it by changing the line
requestMsgSet = sessionManager.CreateMsgSetRequest("US", 2, 0)
requestMsgSet = sessionManager.CreateMsgSetRequest("US", 13, 0)

AmazonS3 GetPreSignedUrlRequest max Expires date

I'm generating pre-signed urls with AmazonS3 .NET SDK. They were working fine but they have stopped working now. I used to set an Expires date near to year 2038 because I wanted to make them as permanent as posible. I used 2038 because that date is an epoch date and there is the Year 2038 problem ( The SDK doesn't limit you on the date but it seems that when you access the url it gives you an Access Denied with the following message:
<Message>Invalid date (should be seconds since epoch): 2147500800</Message>
Does anyone know if there are any limits with the Expires date?
It looks like you already know the answer to this.
A quick test reveals that expiry dates after approximately 03:14 UTC on Tuesday, 19 January 2038 do indeed fail. You've run into the bug in the wikipedia article you linked to.
Confirmed the issue of Year 2038 problem in AWS S3 presignedURL.
I've tested until 01-19-2038 UTC 03:00:00 and it still works.
However, to avoid time screw i choose to use 01-19-2038 UTC 00:00:00

Date range issue

I have shifted our live server to a new server configuration Windows 2008 server and sql server 2008.
But I am having following exception while adding date field data :
2011-05-15 18:00:44,263 ERROR Error
caught : the details of the error are
SqlDateTime overflow. Must be between
1/1/1753 12:00:00 AM and 12/31/9999
11:59:59 PM. at
But the same code is working fine on local machine and was also working fine on old server.
I have even changed the date field explicitly into "mm/dd/yy" format.
But still not found the solution.
Can anyone provide me the solution.
Yes this happens because of server time format changed from your local system.
You should convert to dd/MMM/yyyy hh:mm:ss which should work in all the systems.
Posting your code may suggest you with the modified code for you.
Hey here are a few links to help you with your problem, with what I have read it seems that
the DataTime.MinValue is equivalent to 00:00:00.0000000, January 1, 0001.
so you'll have to change that if you are using it, anyways here are the links
Hope it helped !