- could it be something to do with the ODBC drivers (Visigenic) on the mac? I thought that the Butler WIN 32 ODBC driver was connecting straight to Butler and so there was no interaction between the Butler WIN 32 drivers and the with the ODBC on the mac. Am I correct? I use DAM connections on the Mac so i don't know it the ODBC on the mac works or not.
- were you using T3 or T2000? I tried this with both Mac OS 7.6.2 and also 9.2.2 with the same results.
- were you using the Butler WIN 32 driver on the Butler CD or is there a later version that that?
- did you connect via tcp/ip from the win 2k box to Butler on the Mac directly?
- was there anything different in the setup of the Butler WIN 32 tcp/ip dsn or in the installation of the Butler WIN 32 driver that we need to know?
- There isn't a Windows version of Butler is there, id so is there a demo copy that I can lay my hands on to test this driver with?
- In the Butler log file it is showing the connection between the Win2k box and Butler is successful, and that it finds the data in the database, and then there is an entry "User Disconnection"
- do you have a Butler database the I could connect to via the Net from our Win 32 box to see if it the prob lies with our Win2k box or our Mac.
thanks for your assistance on this one - it is really important that we get this working and fast.
Garth
Any chance you're using a Tango for Access product? Yes there was a release of a product that was similar to Tango for Filemaker but for Access and the windoze platform. I can't remember if it was a 2.x product or 3.x. I used to have a list of the serial number prefixes which identified the exact version of the product but I don't know where it is.Other things to check is that you've set up a system data source, etc. I know that the Win Butler driver works under Win2000 because I've used it. Will that same version connect to any other data source? Hope this helps, Steve Smith Skadt Information Solutions Office: (519) 624-4388 GTA: (416) 606-3885 Fax: (519) 624-3353 Cell: (416) 606-3885 Email: [EMAIL PROTECTED] Web: http://www.skadt.com-----Original Message----- From: [EMAIL PROTECTED] [mailto:owner-witango-talk@;witango.com]On Behalf Of Garth Penglase Sent: October 22, 2002 9:20 PM To: Multiple recipients of list witango-talk Subject: Witango-Talk: T3 tcp/ip db connection (licensing issue?) -- Hi everyone, this is particularly for those who have been around tango for quite a while. I recently installed Tango 3.52 promo version (10 user version) under Win 2k. Originally I was getting stanza probs which we finally were able to resolve (by fluke only though the suggestions from historical and recent entries on this list were useful). Now I am trying to connect from the Win2k box using Butler WIN 32 drivers to a Mac running Butler but when running the taf which uses the tcp/ip DSN I get this message: An error occurred while processing your request: Position: Insert Class: Internal Main Error Number: -109 This type of data source is not supported by the server license. Position: Insert Class: Internal Main Error Number: -4 Unable to connect to the specified data source. Verify that data source is properly configured and that database server is online. I'm sure I remember having connected via tcp/ip from one mac to> another using the same license (actually the Mac version of the > software off the same CD) so I think the server license message is > erroneous. But am I wrong? Is it indeed not possible using thislicense? thanks Garth ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]> with unsubscribe witango-talk in the message body > > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
--
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
