Well that may be true. I don't expect FMI really expects client to be used this way. It's not something I have ever done except back in 5 days.
You could try using the XODBC install from server and see if that fixes it for client. Dan Stein MSN, CPNP FileMaker 7 Certified Developer FileMaker 9 Certified Developer Digital Software Solutions 303 W. Chestnut St Souderton PA 18964 Land: 215-799-0192 Cell: 610-256-2843 FMP, WiTango,MSSQL, MySQL,PHP d...@dss-db.com www.dss-db.com “Success comes from knowing that you did your best to become the best that you are capable of becoming.” On Aug 22, 2011, at 7:48 AM, Wayne Irvine wrote: > Nope, it is fixed with the server but not FMP. Have tried both .76 and .81 of > the xbdc listener. > > Wayne > > On 22/08/2011, at 8:19 PM, d...@dss-db.com wrote: > >> This was fixed with V3 of the server. I worked closely with FMI to get it >> fixed and they came through. Load the latest version and it will disappear. >> >> Dan >> >> >> Sent from My Web Mail Account >> Dan Stein MSN, CPNP, EMT-B >> d...@dss-db.com >> www.dss-db.com >> land: 215-799-0192 >> >> >> From: "Wayne Irvine" <wa...@byteserve.com.au> >> Sent: Sunday, August 21, 2011 8:29 PM >> To: Witango-Talk@witango.com >> Subject: Witango-Talk: Terascript/FileMaker Pro >> >> As you know I am a big fan of using Witango/Terascript with FileMaker Pro >> (client) as a datasource. It worked well in FileMaker 6 that it survived >> until a working FileMaker 11 solution was developed. >> >> I need to report a bug however. The fmxdbc_listener process which forms a >> bridge between Terascript and FileMaker has a memory leak. Over time it's >> memory foot print grows from 95Mb up to about 1.5Gb when it crashes on my >> server. >> >> FileMaker are aware of the bug and working on a solution although I get the >> feeling it's not a very high priority for them as they can give no time >> frame on a fix. >> >> Just thought you all (or more likely 'both' ;) ) should know. >> >> Wayne Irvine >> >> ---------------------------------------- >> >> To unsubscribe from this list, please send an email to lists...@witango.com >> with "unsubscribe witango-talk" in the body. >> >> >> To unsubscribe from this list, please send an email to lists...@witango.com >> with "unsubscribe witango-talk" in the body. > > > To unsubscribe from this list, please send an email to lists...@witango.com > with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body.