Ben Johansen wrote:
Hi John,
I remember the discussion on this but can't seem to find it :-(
I think it was asked and I think they worked on improving the speed...
But, with the database being a fluid target, I can see why this would be a
touchy subject. You make changes to a TAF which has a old schema for a table
that was updated on the server... you get the picture
Not all DB's are fluid targets. Like the one I'm trying to connect to.
On thing I did for one situation was I created a way to convert SQL Server
Schema to Access Schema and so I would connect to a local Access DB and
would periodically update the schema.
Right now I think I'm just going to try to remeber to not close my
Witango Studio for no reason and limit the amount of times that it's
forced to get the schema again.
/John
Ben Johansen - http://www.pcforge.com
Authorized Witango & MDaemon Reseller
Available for Web App. Developement
-----Original Message-----
From: John McGowan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 15, 2005 9:49 AM
To: [email protected]
Subject: Witango-Talk: Data Source Information Caching
I seem to remember this topic coming up before... But I'm not sure where...
Is there a way to get the Witango Dev studio to try to cache the
information it has about a particular data source, so every time you
connect to it it doesn't go out and gather all the information about
it. I have a new remote data source that is a little slow in reporting
all that information which causes the dev studio to take quite a while
to load.
I could swear I heard someone else talking about this, or read it somewhere.
/John
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
