[AccessD] Change ODBC timeout default query property

Thanks Gustav 
But the problem is two fold. It is not for just existing queries but for
when they are making new queries. Forget to update the query property
and a special message pops up.   I know immediately I forgot when I get
the message and reset. Others don't understand the message and I usually
have to remind them.
 
I need a way to change this without having users run something special.

**************************************************
* Patricia O'Connor
* Associate Computer Programmer Analyst
* OTDA - BDMA
* (W) mailto:Patricia.O'Connor at otda.state.ny.us
* (w) mailto:aa1160 at nysemail.state.ny.us
**************************************************
 

> 
--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments.  Please notify the sender immediately by reply e-mail and delete the e-mail from your system. 


-----Original Message-----

> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> Gustav Brock
> Sent: Tuesday, August 22, 2006 10:41 AM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] Change ODBC timeout default query property
> 
> Hi Patricia
> 
> You can set that property using DAO:
> 
>   CurrentDb.QueryDefs("qdyYourQuery").ODBCTimeout = 600
> 
> Of course, to carry this out create a loop that somehow 
> filters only those querydefs that have to be modified.
> 
> /gustav
> 
> >>> Patricia.O'Connor at otda.state.ny.us 22-08-2006 15:46:57 >>>
> Hi all 
> 
> Is there a way to set the ODBC timeout default  in the query 
> properties from 60 to 6000 permanently?  Most of our work is 
> against our ORACLE databases, some Foxpro, and SqlServer. For 
> every new query we do we have to remember to reset this 
> before running otherwise we get a timeout.
> Does not matter how easy or hard the query is, If it isn't at 
> least 600 then poof it stops.  One person said that it would 
> cause their MDB to corrupt but I haven't had that problem.  
> 
> The OPTIONS ADVANCED does not do this.  I have looked almost 
> everywhere but can't find out how to change the default.  
> This would be for 2k or 2k3.
> Any help appreciated 
> 
> Thanks
> 
> **************************************************
> * Patricia O'Connor