From Newsgroup: comp.databases.ms-sqlserv

I am having huge issues with my database front end constantly corrupting. It's becoming a real problem. On my desktop, I am running Windows 10 and Microsoft 365. On the backend computer, I am running Windows Server 2016 and MS Office 2019. I guess I'll start using the server for my development, but I wanted to see if others are experiencing issues with corruption on Microsoft 365. I'm going to start using Office 2019 to see if it is any better. Thoughts?
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.databases.ms-sqlserv

On 2/15/2023 1:58 PM, musicloverlch wrote:

I am having huge issues with my database front end constantly corrupting. It's becoming a real problem. On my desktop, I am running Windows 10 and Microsoft 365. On the backend computer, I am running Windows Server 2016 and MS Office 2019. I guess I'll start using the server for my development, but I wanted to see if others are experiencing issues with corruption on Microsoft 365. I'm going to start using Office 2019 to see if it is any better. Thoughts?

I've been running Office 365 on this Win10 computer for years without
problems such as you're describing.

I'm not sure what you mean by "backend computer"...but my server has had
no problem with any version of MS database for decades. However, it is important to carefully integrate the interaction between 365 computers
and the server. So, it sounds to me that your database structure is the problem.
--
best regards,

Neil

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.databases.ms-sqlserv

On Wednesday, February 15, 2023 at 1:19:28 PM UTC-6, Neil wrote:

On 2/15/2023 1:58 PM, musicloverlch wrote:

I am having huge issues with my database front end constantly corrupting. It's becoming a real problem. On my desktop, I am running Windows 10 and Microsoft 365. On the backend computer, I am running Windows Server 2016 and MS Office 2019. I guess I'll start using the server for my development, but I wanted to see if others are experiencing issues with corruption on Microsoft 365. I'm going to start using Office 2019 to see if it is any better. Thoughts?

I've been running Office 365 on this Win10 computer for years without problems such as you're describing.

I'm not sure what you mean by "backend computer"...but my server has had
no problem with any version of MS database for decades. However, it is important to carefully integrate the interaction between 365 computers
and the server. So, it sounds to me that your database structure is the problem.

--
best regards,

Neil

Thanks, Neil. I appreciate your input. I did find this Microsoft article that was last updated in January 2023. https://support.microsoft.com/en-us/office/fixes-or-workarounds-for-recent-issues-in-access-54962069-14f4-4474-823a-ff7e5974a570
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.databases.ms-sqlserv

On 2/15/2023 2:35 PM, musicloverlch wrote:

On Wednesday, February 15, 2023 at 1:19:28 PM UTC-6, Neil wrote:

On 2/15/2023 1:58 PM, musicloverlch wrote:

I am having huge issues with my database front end constantly corrupting. It's becoming a real problem. On my desktop, I am running Windows 10 and Microsoft 365. On the backend computer, I am running Windows Server 2016 and MS Office 2019. I guess I'll start using the server for my development, but I wanted to see if others are experiencing issues with corruption on Microsoft 365. I'm going to start using Office 2019 to see if it is any better. Thoughts?

I've been running Office 365 on this Win10 computer for years without
problems such as you're describing.

I'm not sure what you mean by "backend computer"...but my server has had
no problem with any version of MS database for decades. However, it is
important to carefully integrate the interaction between 365 computers
and the server. So, it sounds to me that your database structure is the
problem.

--
best regards,

Neil

Thanks, Neil. I appreciate your input. I did find this Microsoft article that was last updated in January 2023. https://support.microsoft.com/en-us/office/fixes-or-workarounds-for-recent-issues-in-access-54962069-14f4-4474-823a-ff7e5974a570

These "fixes" may not be relevant to your situation, but you might try

it to see if they were. If so, please let me know that it solved your problems!

They appear to me to be integrating Access 365 functions interactively
with server DB functions, and if so, the "fixes" will only work if all
aspects of the DB configuration and integration are done correctly. That
will not be simple.
--
best regards,

Neil

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.databases.ms-sqlserv

On Wednesday, February 15, 2023 at 12:58:57 PM UTC-6, musicloverlch wrote:

I am having huge issues with my database front end constantly corrupting. It's becoming a real problem. On my desktop, I am running Windows 10 and Microsoft 365. On the backend computer, I am running Windows Server 2016 and MS Office 2019. I guess I'll start using the server for my development, but I wanted to see if others are experiencing issues with corruption on Microsoft 365. I'm going to start using Office 2019 to see if it is any better. Thoughts?

Any chance some one is accessing the backend using WIFI to connect to the network?
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.databases.ms-sqlserv

Am 15.02.23 um 19:58 schrieb musicloverlch:

I am having huge issues with my database front end constantly corrupting. It's becoming a real problem. On my desktop, I am running Windows 10 and Microsoft 365. On the backend computer, I am running Windows Server 2016 and MS Office 2019. I guess I'll start using the server for my development, but I wanted to see if others are experiencing issues with corruption on Microsoft 365. I'm going to start using Office 2019 to see if it is any better. Thoughts?

Hallo / Hi,
do a search for "DisableLeasing". Not sure if this helps in your case.

Dirk
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.databases.ms-sqlserv

On Wednesday, February 15, 2023 at 1:58:57rC>PM UTC-5, musicloverlch wrote:

I am having huge issues with my database front end constantly corrupting. It's becoming a real problem. On my desktop, I am running Windows 10 and Microsoft 365. On the backend computer, I am running Windows Server 2016 and MS Office 2019. I guess I'll start using the server for my development, but I wanted to see if others are experiencing issues with corruption on Microsoft 365. I'm going to start using Office 2019 to see if it is any better. Thoughts?

I had a recent problem with Microsoft 365 Access 2016 connected to a SQL Server backend. The corruption wouldn't let me make any changes to code without an ODBC error coming up. Copying controls didn't solve the problem, so I built a form to rebuild a form control by control. I simply omitted any control properties that caused an error. Note that a FontWeight of Semi-bold wouldn't copy over correctly. The amount of code is a bit long to put here, but I can try to make it available to you if you'd like.
James A. Fortune
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.databases.ms-sqlserv

On Thu, 16 Feb 2023 11:47:10 -0500, Neil <neil@myplaceofwork.com>
wrote:

On 2/15/2023 2:35 PM, musicloverlch wrote:

On Wednesday, February 15, 2023 at 1:19:28 PM UTC-6, Neil wrote:

On 2/15/2023 1:58 PM, musicloverlch wrote:

I am having huge issues with my database front end constantly corrupting. It's becoming a real problem. On my desktop, I am running Windows 10 and Microsoft 365. On the backend computer, I am running Windows Server 2016 and MS Office 2019. I guess I'll start using the server for my development, but I wanted to see if others are experiencing issues with corruption on Microsoft 365. I'm going to start using Office 2019 to see if it is any better. Thoughts?

I've been running Office 365 on this Win10 computer for years without
problems such as you're describing.

I'm not sure what you mean by "backend computer"...but my server has had >>> no problem with any version of MS database for decades. However, it is
important to carefully integrate the interaction between 365 computers
and the server. So, it sounds to me that your database structure is the
problem.

--
best regards,

Neil

Thanks, Neil. I appreciate your input. I did find this Microsoft article that was last updated in January 2023. https://support.microsoft.com/en-us/office/fixes-or-workarounds-for-recent-issues-in-access-54962069-14f4-4474-823a-ff7e5974a570

These "fixes" may not be relevant to your situation, but you might try

it to see if they were. If so, please let me know that it solved your >problems!

They appear to me to be integrating Access 365 functions interactively
with server DB functions, and if so, the "fixes" will only work if all >aspects of the DB configuration and integration are done correctly. That >will not be simple.

After changing to MSoft365 my database had all the combo boxes
slightly elongated.
--- Synchronet 3.21d-Linux NewsLink 1.2