Azure backend of database timing out?

Hello All

I have a database where the front end is on everyone's computers and the backend is up on Azure.  When someone leaves the front end on (for example if they go to lunch) when they come back it is as if the backend disconnected.  They have to restart the frontend in order to reconnect.

Is there something in Azure where I can tell it to not disconnect if there is no activity?  Or is there something I can add to the frontend in Access that continually pings the backend so that it thinks someone is there?

Thanks
alevin16Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bill RossProgrammerCommented:
Hi,

In your front end create a bound form. Set the recordsource to a little used table.  Open it invisible when the user opens the front end.  That will maintain a persistent link to the DB and prevent time out.

Regards,

Bill
0
Nick67Commented:
@Bill Ross's suggestion may or may not work with Azure, but it is certainly worth trying.
What he is describing is an old performance enhancing trick that should be used on any FE/BE application that uses DAO.
Such applications perform better when a connection they make to the backend persists for the entire lifetime of the application.  In my application, I have 'tblDummy' that has a text field (field1) and a timestamp field(SSMA_Timestamp).  In the application, I have 'frmDummy' that is based off that table with a textbox (field1).  The OnLoad event of the start up form of the application calls
DoCmd.OpenForm "frmDummy", acNormal, , , , acHidden
That form sits quietly in the background, hidden, persisting the connection to the database.

That may or may not be enough for Azure.

But we could extend the idea.
My dummy form does nothing.  Yours could do something on a timer interval
Sub Form_Load()
Me.TimerInterval = 1200000 '20 minutes
End Sub

Sub Form_Timer()
Me.Field1.Requery
End Sub

Open in new window


So, once every 20 minutes, the form will requery its control.
That may be enough to keep Azure from timing out.

Nick67
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
alevin16Author Commented:
Thank you very much!
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Gustav BrockCIOCommented:
But what was the solution?

/gustav
0
alevin16Author Commented:
Hi Gustav

I was able to use the trick above where I have a dummy form and I refresh it every 15 minutes.  It worked nicely.
0
Gustav BrockCIOCommented:
Thanks!

/gustav
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.