MS Access 2016 in Office PRO 2016 will not open DB created in Microsoft 365

[ebolbol]

You know... you would think Microsoft would provide patches for a situation like this. Reading all the Microsoft Support Community posts, it appears, if your in a situation like this, you're pretty much screwed. Have any of you encountered a similar situation?



The database file was created in Microsoft® Access® for Microsoft 365 MSO (Version 2208 Build 16.0.15601.20676) 64-bit


In 2016 I paid full price for Microsoft Office PRO 2016 64-bit. It will not open the above DB and generates this message:



Please share your experience at your leisure.

Thx,

Ed

[CJ_London]

Apps are usually backwards compatible but not forward compatible. Both 2016 and 365 are a 2016 version of access and I would expect it to be openable providing the 365 version does not utilise options not available 7 years ago.

the standard advice is to develop in the earliest version users will be using

[isladogs]

There's practically nothing new in A365 that wasn't in A2016
However, one likely cause is that you ticked the option to support the date time extended datatype for linked SQL Server tables.
That changes the database structure.
A2016 didn't have that setting so cannot open the file

[ebolbol]

Apps are usually backwards compatible but not forward compatible. Both 2016 and 365 are a 2016 version of access and I would expect it to be openable providing the 365 version does not utilise options not available 7 years ago.

the standard advice is to develop in the earliest version users will be using

Thanks CJ_London, yeah.... that seems to be the consensus on the www. All that work, now I have to do it in the earlier version. There is an emoji for this.... let me see if I can find it.... oh... yeah...

[ebolbol]

There's practically nothing new in A365 that wasn't in A2016
However, one likely cause is that you ticked the option to support the date time extended datatype for linked SQL Server tables.
That changes the database structure.
A2016 didn't have that setting so cannot open the file

@isladogs, I think you are thinking exactly on the right track. The only thing different from a version of the db file that I WAS able to open and not able anymore is I added 4 calculated fields in the table with long expressions to calculate date. Once I did that, 2016 PRO would not play ball anymore.

[ebolbol]

There's practically nothing new in A365 that wasn't in A2016
However, one likely cause is that you ticked the option to support the date time extended datatype for linked SQL Server tables.
That changes the database structure.
A2016 didn't have that setting so cannot open the file

@isladogs, once I added these calculated fields in the table, Access 2016 PRO said, nope! can't do that!

[CJ_London]

I’m surprised that calculation works as lessmeal is short text, not a number

edit: however just tried it and it does work as a calculation

[ebolbol]

I’m surprised that calculation works as lessmeal is short text, not a number

edit: however just tried it and it does work as a calculation

yes it works well... but I believe these fields are the reason my version 16 won't open the db. However, below is Microsoft's explanation as to why this is happening, does this mean anything to you Access Pro's?

This issue occurs if you try to open a database that contains a table that uses the BigInt data type. BigInt support was added to Access 2016. BigInt appears within the table's data type as Large Number.
I'm not using BigInt... I'm using calculated....

[CJ_London]

perhaps correct the datatype - it might make a difference

Otherwise don't use calculated fields - most developers don't recommend them anyway - do your calculations in a query, form or report as and when required

another thought since you have use of 2016 - create your tables in 2016 with your calculated fields - does than then work in 365?

[ebolbol]

perhaps correct the datatype - it might make a difference

Otherwise don't use calculated fields - most developers don't recommend them anyway - do your calculations in a query, form or report as and when required

another thought since you have use of 2016 - create your tables in 2016 with your calculated fields - does than then work in 365?

I will try that. In the form, I want the user to be able to enter time in, time out and calculations to immediately be performed on the fields in the record they are on. That's how the form works now. A query would kind of complicate this, no?

[isladogs]

No.
A query is ideal for running calculations. There is rarely any benefit in storing calculated values in a table and several disadvantages

[ebolbol]

No.
A query is ideal for running calculations. There is rarely any benefit in storing calculated values in a table and several disadvantages

Huh... very interesting. I will definitely play with it to see if I can make that happen. Here is the db. Who ever thinks they have any use for this, you're welcome to it.

Rgds,

Ed

[CJ_London]

I used this query for your form

SELECT
DailyLog.*,
IIf((([TimeOut]-[TimeIn])*24)-[LessMeal]<9,(([TimeOut]-[TimeIn])*24)-[LessMeal],9) as cTime,
IIf(((([TimeOut]-[TimeIn])*24-[LessMeal])-[CTime])<3,((([TimeOut]-[TimeIn])*24-[LessMeal])-[CTime]),3) as cOT,
((([TimeOut]-[TimeIn])*24)-[LessMeal]-[CTime])-[COT] as cDT,
[CTime]+[COT]+[CDT] as cTtl
FROM DailyLog;

and modified the bound controls to use these rather than your calculated values




and works same as before with calculated fields - only difference is the calcs don't show until the record is saved.

You can get round that by putting the calculations into unbound controls using reference to the controls - e.g.












etc

[ebolbol]

I used this query for your form


and modified the bound controls to use these rather than your calculated values




and works same as before with calculated fields - only difference is the calcs don't show until the record is saved.

You can get round that by putting the calculations into unbound controls using reference to the controls - e.g.





etc

can you attach the modified db? ha ha ha ha I'm not at your level, I'd like to see it

[CJ_London]

I told you everything you need to know - if you don't do it yourself, you'll never learn

but attached as requested

DailyLog - the first method (changing the form recordsource)
Dailylog2 - the second method (using unbound controls)
DailylogOld - your original version

I note you are using a split form - these have their limitations but providing you don't wat to do anything 'adventurous', should not be a problem