cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Level 1

setting date password inconsistency after update

We work with QB Desktop Pro 2019, 3 users, data on server.

One of our computers has the date formatted dd/mm/yyyy, the other 2 have the setting mm/dd/yyyy.

Up to the QB 2018 Pro version, we always set the closing password on the computer with dd/mm/yyyy, and the others didn't have any kind of problems recognizing the date format.

After installing QB 2019 Pro R3, the computers with a different date format than the one that set the Closing Date password, were not able to post any transactions, as the system kept popping up the window saying that the transaction would affect prior fiscal years, and the P/W is needed to post it, even though it was the current date, 3 months after the YE date.

After digging through several options, I noticed that all the computers using QB, need to be set up with the same date format as the closing date P/W was set up.

This wasn't the case on prior versions before installing QB 2019 Pro, as we work with QB Pro since 1997, and never had this issue. 

Why this change that complicates everything. Shouldn't QB be able to recognize the date format on each computer, independently of the way it's set up, as it did in prior versions?

Please go back to the old system and allow different date formats to be recognized by QB.

 

Solved
Best answer December 07, 2018

Best Answers
Highlighted
Level 15

setting date password inconsistency after update

"Shouldn't QB be able to recognize the date format on each computer"

 

You cannot Mix the settings for a multi-user environment. And even for a single-user system, the Program you bought needs to be matched to the Operating System settings. Example: QB for US = Windows Region, Language, currency, etc as US.

View solution in original post

1 Comment
Highlighted
Level 15

setting date password inconsistency after update

"Shouldn't QB be able to recognize the date format on each computer"

 

You cannot Mix the settings for a multi-user environment. And even for a single-user system, the Program you bought needs to be matched to the Operating System settings. Example: QB for US = Windows Region, Language, currency, etc as US.

View solution in original post

Need to get in touch?

Contact us