# QAD MFG - OpenEdge DB Querying **URL:** \ **Category:** Ignition\ **Tags:** ignition79, database\ **Created:** [January 5, 2018, 11:12pm UTC](https://forum.inductiveautomation.com/t/qad-mfg-openedge-db-querying/16495 "2018-01-05T23:12:23Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![bfuson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfuson/32/4597_2.png) [@bfuson](https://forum.inductiveautomation.com/u/bfuson)\ **Post date:** [January 5, 2018, 11:12pm UTC](https://forum.inductiveautomation.com/t/qad-mfg-openedge-db-querying/16495/1 "2018-01-05T23:12:23Z")
I’m attempting to pull live customer order information from an existing ERP system (QAD MFG). The backing data store for their system is a Progress OpenEdge Database. I’ve successfully installed the OpenEdge JDBC driver in Ignition, can query successfully, and can see all tables/columns in Ignitions Query Browser Tool. The problem is, I can’t seem to query the right data. The entity model used by QAD is complex, and after referencing their [official technical document](https://documentlibrary.qad.com/documents/2370665/2368142/EntityDiagrams_TR_v2012_1EE.pdf), the queries I do write seem to always time out if they work at all. Checking the gateway logs reveals the queries take 2-5 minutes, which is enough time for my designer to have a socket-timeout exception and drop the gateway connection entirely. **Can I configure the gateway to wait longer for queries to return, or do I have other options here?** Any help or advice would be greatly appreciated. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 6, 2018, 12:03am UTC](https://forum.inductiveautomation.com/t/qad-mfg-openedge-db-querying/16495/2 "2018-01-06T00:03:06Z")
There is a URL option for socketTimeout in the [MySQL JDBC driver](https://docs.inductiveautomation.com/display/DOC79/Connecting+to+MySQL) – there might be something similar for the OpenEdge driver, too. Also, there is a per-project setting for query timeouts from clients and designers that you will probably have to raise. ---
**Author:** ![bfuson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfuson/32/4597_2.png) [@bfuson](https://forum.inductiveautomation.com/u/bfuson)\ **Post date:** [January 15, 2018, 6:15pm UTC](https://forum.inductiveautomation.com/t/qad-mfg-openedge-db-querying/16495/3 "2018-01-15T18:15:23Z")
Unfortunately the driver supplied had no URL options for this, and I wasn’t able to find the per-project setting. I was able to circumvent the Query Browse problem by making a scanclass with a long delay (5 minutes) and setting a Query Tag to the desired query. Debugging is slow, but at least I get the data! Thanks for your suggestions! ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 15, 2018, 6:36pm UTC](https://forum.inductiveautomation.com/t/qad-mfg-openedge-db-querying/16495/4 "2018-01-15T18:36:17Z")
> [@bfuson](#): > > I wasn't able to find the per-project setting Did you look at the "Timing" Section of [Project Properties](https://docs.inductiveautomation.com/display/DOC79/Project+Properties)? ---
**Author:** ![bfuson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfuson/32/4597_2.png) [@bfuson](https://forum.inductiveautomation.com/u/bfuson)\ **Post date:** [January 15, 2018, 6:49pm UTC](https://forum.inductiveautomation.com/t/qad-mfg-openedge-db-querying/16495/5 "2018-01-15T18:49:17Z")
I did, but had only changed the “Connect” Timeout previously, as my designer client was the thing disconnecting 😥 Upping the Read Timeout fixed the issue though, thanks! I wish the Query Browser window displayed something like “Query timed out after XX.XX seconds…” instead of throwing a socket timeout exception when query execution exceeds the project read timeout.