Delay in processing, migrated to MS SQL backend

[Gina Maylone]

Good morning all!

I have recently taken a stab at moving my back end tables to MS SQL 2014. The migration went pretty well I think. However, there is a delay whenever I search for, or add records. Is this common? Would it matter if I put it on a more expensive server (I went cheap for testing purposes)? I also get a Write Conflict when entering scheduling information, I have checked all the bit fields and defaulted them to "0" as I read somewhere. It's a bit frustrating. Is there another back end option? I have read that Access Web Apps are being deprecated - and I'm not looking for a web app. Just to share data among users. Thank you in advance!

[ranman256]

I ran in SQL backend just fine. Tho, my SQL hated bit fields. They caused problems, so I had to use INTEGER. Then it worked fine.

[Gina Maylone]

Thanks RanMan, I just tried changing bits to int and still get a write conflict. So you never experienced a delay in processing speed?

[Gina Maylone]

Thanks RanMan, I just tried changing bits to int and still get a write conflict. So you never experienced a delay in processing speed?

[Gina Maylone]

Sorry for the double post above. ??? Anyway, for the knowledge of future generations, I figured out my write conflict was being caused by using a subform to schedule people. The linked master field would update once I entered the subform, without a save command, and I would enter the date and time fields causing the conflict. I added a save record command in the On Got Focus event and it took care of the problem.