The URL Scripting approach is what I use. I agree it is slow. For a  
Sybase database we have an app that uses Sybase drivers and I send it  
SQL via applescript and it sends back results. That is faster than  
the URL Scripting system. So if you can build an app that talks to  
MySQL directly, and make it receive and reply to AppleEvents, that  
will probably work better for you.

I agree, HC is still very useful. I'm not sure why Apple thinks  
AppleScript is as easy to use as HyperTalk. Sure do wish Apple would  
create a HyperTalk scripting addition.

Kee Nethery


On Mar 22, 2006, at 5:21 AM, Lloyd Butler wrote:

> I know HC is a dead app, but it is still very useful.
>
> I currently have HC talking to FileMaker via applescript in about  
> 50 stacks used daily, but want to move to MySql so that the db can  
> be run on other hardware if need be.
>
> HC does not seem to understand the "do shell script" in a  
> applescript stored in an object. I do not want to store the text of  
> the script in a field, and have it compiled each time I call it, so  
> I have not tried that route.
>
> Using a cgi to handle the database communications, URL Scripting  
> looks to get back a file. So if I made a call to the cgi from HC, I  
> would then need to read the resulting file, too many steps and too  
> slow.
>
> I have to check to see if Interarchy can get back a http request  
> into a variable. If so, then I guess I could try that out. HC <->  
> Interachy <-> cgi <-> MySql
>
> Short of ditching HC, which will need to be done now with Intel  
> machines, does any one have any other ideas or suggestions?
>
> Thanks for any ideas.
>
> Lloyd