And you will love the ODBC in FMP 11 no need for special layouts or worrying 
about where fields are. Just query a table like you would SQL.

I do suggest when you move to 11 you also move to the multiple table system so 
you don't need more then one data file and one UI file.

I have tools and have done that many times if you need help.

With that kind of system you also then build a fMP ODBC table that just 
references the tables in the data file that you need. end up giving you are 
SQWL like structure to work with and faster response.

Contact me off list if you need more explanation.

Robert if you want me to try and write up something on FMP 9,10,11 and Witango 
let me know.
--
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
Fax 215-799-0192 ( Call 1st)
FMP, WiTango,MSSQL, MySQL,PHP
[email protected]
www.dss-db.com


'I wonder why we say that people are of different "races". It seems to me, 
we're all running at the same speed and heading towards the same destination. 
The only "winners" are the ones who've made the world a better place for having 
been here.'
>From for Better or Worse 2/28/2006 view this comic at
http://catalog.fborfw.com/indexdate.php?q=2006-02-28&Submit=Search








On Aug 12, 2010, at 7:54 PM, Wayne Irvine wrote:

> Thank Robert, this is music to my ears.
>
> We run a range of Witango 5.5 servers on G5s with FileMaker 6 as a backend. 
> All development is done on Intel Macs but is beginning to get a bit clunky.
>
> A modern Witango 6 running on Intel Macs with FileMaker 11 is exactly what we 
> have been waiting for (in our wildest dreams).
>
> Any assistance we can offer in terms of testing, conversion, or marketing 
> (particularly down under) let me know. Very keen to see this succeed.
>
> Wayne Irvine
>
>
>
> On 13/08/2010, at 8:44 AM, "Robert Shubert" <[email protected]> wrote:
>
>> Chuck,
>>
>> The exact specs of 6 haven't been hammered out, and some platforms and 
>> configurations may not be supported until a subsequent '6.1' release, but I 
>> can tell you that on the Mac side I am working on Intel hardware, Mac OS X 
>> 10.6 and Java 1.6. This platform will be fully supported. I hope to be able 
>> to support 10.5 on Intel as well. I have already made the decision not to 
>> support PowerPC hardware. This seems to be an acceptable stance in the 
>> market today, not only has Apple dropped support for PowerPC in 10.6, but 
>> other vendors are announcing similar moves.
>>
>> Robert
>> Witango
>>
>> -----Original Message-----
>> From: Chuck Leavens [mailto:[email protected]]
>> Sent: Thursday, August 12, 2010 4:45 PM
>> To: [email protected]
>> Subject: Re: Witango-Talk: Still using Tango 2000?
>>
>> Will v6 be OSX/Intel compatible?
>>
>>
>> On Aug 12, 2010, at 4:17 PM, Robert Shubert wrote:
>>
>>> WebDude & anyone else still using Tango 2000…
>>>
>>> I’ve updated the page on the Witango.com site (Products > What’s New) so 
>>> that it has working links to the two “What’s New” documents. The top part 
>>> of the page talks about migration from Tango 2000 to Witango 5. The bottom 
>>> part is about moving from 5.0 to 5.5.
>>>
>>
>>
>>
>> Chuck Leavens
>> Dir. of Engineering and I.T.
>> WDUQ Pittsburgh Public Radio
>> Pittsburgh PA 15219
>> 412-396-5508
>>
>>
>>
>>
>>
>>
>> ----------------------------------------
>>
>> To unsubscribe from this list, please send an email to [email protected] 
>> with "unsubscribe witango-talk" in the body.
>>
>>
>>
>> ----------------------------------------
>>
>> To unsubscribe from this list, please send an email to [email protected] 
>> with "unsubscribe witango-talk" in the body.
>>
>
>
> ----------------------------------------
>
> To unsubscribe from this list, please send an email to [email protected] 
> with "unsubscribe witango-talk" in the body.



----------------------------------------

To unsubscribe from this list, please send an email to [email protected] 
with "unsubscribe witango-talk" in the body.

Reply via email to