Leopard compatibility?

FileMaker Inc. have published a page on their web site warning that
FileMaker products may have compatibility issues with Mac OS X 10.5
"Leopard". They are working on updates for the FileMaker 9 series, but
the situation is uncertain for earlier versions and there might be no
official word.



Just a heads-up at this stage. Don't rush to install Leopard on
development or production computers.

Does anyone recall similar problems with earlier major updates of Mac OS
X? I'm able to run FileMaker Pro 6 and 7 on Tiger and I'm not aware of
any issues they had. I know several people still running versions 6, 7
and 8.5 who are likely to want to upgrade to Leopard but aren't too keen
to upgrade to a later version of FileMaker.

Also of note: Leopard apparently no longer includes the Classic
environment, which means it will not be possible to run FileMaker 5.0 or
earlier on Leopard (short of a third-party PowerPC or 68K emulator).

This could affect anyone needing to maintain a FileMaker 3 or 4
database, requiring the use of an older system or another computer.

Anyone maintaining a 5.0 database would need to get hold of 5.5 or 6.0,
which will run natively on Mac OS X (assuming they are compatibile with
Leopard).

--
David Empson
dempson@actrix.gen.nz

Re: Leopard compatibility?

In article <1i6e4tc.4a2keonlltl6N%dempson@actrix.gen.nz>,
dempson@actrix.gen.nz (David Empson) wrote:

> Also of note: Leopard apparently no longer includes the Classic
> environment, which means it will not be possible to run FileMaker 5.0 or
> earlier on Leopard (short of a third-party PowerPC or 68K emulator).

I know I only have to wait 4 days for a definitive answer, but I'd
really like to see some actual evidence for all the comments about
Classic going away. The biggest arguments in favor of its absence seem
to be a lack of evidence of its presence, but the same rumors were
floating around for the same reasons (lack of explicit mention of its
survival) when 10.4 was nigh-shipping, and as abrupt as some of Apple's
changes have been, I don't recall them ever doing anything _that_
potentially disruptive without even a peep by the time preordering was
available.

Re: Leopard compatibility?

Gregory Weston wrote:

> In article <1i6e4tc.4a2keonlltl6N%dempson@actrix.gen.nz>,
> dempson@actrix.gen.nz (David Empson) wrote:
>
> > Also of note: Leopard apparently no longer includes the Classic
> > environment, which means it will not be possible to run FileMaker 5.0 or
> > earlier on Leopard (short of a third-party PowerPC or 68K emulator).
>
> I know I only have to wait 4 days for a definitive answer, but I'd
> really like to see some actual evidence for all the comments about
> Classic going away.

The only ones with actual evidence as to whether or not Classic is still
there are developers, and they can't say anything definite about it or
they will violate their NDA. Apple have said nothing either way.

As you say, we can find out for certain in four days.

If Classic support is essential to you, hold off purchasing Leopard
until you have a definite answer.

> The biggest arguments in favor of its absence seem to be a lack of
> evidence of its presence,

It is stronger than that. I've seen mention of earlier developer builds
saying "You can not start up Classic because Classic is not supported on
Mac OS X 10.5". This is hearsay, of course.

> and as abrupt as some of Apple's
> changes have been, I don't recall them ever doing anything _that_
> potentially disruptive without even a peep by the time preordering was
> available.

The computer will still be able to boot Tiger, so there is still a way
to run Classic (or boot Mac OS 9 directly, if the computer is old
enough). I agree that this would be seriously disruptive if you need to
run Leopard and Classic applications at the same time. A second computer
would seem to be a better option.

Getting back on topic, how many FileMaker 3 and 4 solutions are there
still in active use? I'm aware of one which was going to be a potential
upgrade job for me to do, but which hasn't eventuated. They will be
finding it increasingly difficult to support if it requires maintaining
an old operating system and computer hardware in order to function.

I expect Windows users have a similar problem - old versions of
FileMaker Pro aren't officially supported on later versions of Windows.

--
David Empson
dempson@actrix.gen.nz

Re: Leopard compatibility?

In article <1i6etvh.1h9fyu614lvibeN%dempson@actrix.gen.nz>,
dempson@actrix.gen.nz (David Empson) wrote:

> Gregory Weston wrote:
>
> > In article <1i6e4tc.4a2keonlltl6N%dempson@actrix.gen.nz>,
> > dempson@actrix.gen.nz (David Empson) wrote:
> >
> > > Also of note: Leopard apparently no longer includes the Classic
> > > environment, which means it will not be possible to run FileMaker 5.0 or
> > > earlier on Leopard (short of a third-party PowerPC or 68K emulator).
> >
> > I know I only have to wait 4 days for a definitive answer, but I'd
> > really like to see some actual evidence for all the comments about
> > Classic going away.
>
> The only ones with actual evidence as to whether or not Classic is still
> there are developers, and they can't say anything definite about it or
> they will violate their NDA. Apple have said nothing either way.
>
> As you say, we can find out for certain in four days.
>
> If Classic support is essential to you, hold off purchasing Leopard
> until you have a definite answer.

For me, Classic is still moderately useful and Leopard is essential. But
keeping bootable installs of the last 2 major versions is also standard
practice so at worst I'm inconvenienced.

I'm just confused about how insistent people have gotten over the last
few months that an absence of evidence counts as evidence of absence.

But this is OT, so I'll let it sit.

G

Re: Leopard compatibility?

David Empson wrote:

> The computer will still be able to boot Tiger, so there is still a way
> to run Classic (or boot Mac OS 9 directly, if the computer is old
> enough). I agree that this would be seriously disruptive if you need to
> run Leopard and Classic applications at the same time. A second computer
> would seem to be a better option.

could Parralels or VMware Fusion run both Leopard and Tiger on the same
time ?
--
www.D-L-S.org

Re: Leopard compatibility?

manet wrote:

> David Empson wrote:
>
> > The computer will still be able to boot Tiger, so there is still a way
> > to run Classic (or boot Mac OS 9 directly, if the computer is old
> > enough). I agree that this would be seriously disruptive if you need to
> > run Leopard and Classic applications at the same time. A second computer
> > would seem to be a better option.
>
> could Parralels or VMware Fusion run both Leopard and Tiger on the same
> time ?

No. Apple doesn't allow Mac OS X to run in a virtual machine. (I think
this is a restriction they should relax, as long as it is running on
Apple hardware.)

Even if it could, it wouldn't help. Parallels and VMware Fusion run on
Intel Macs, and are virtual machines for hosting an Intel operating
system.

You can't run Classic on an Intel Mac at all. It requires a PowerPC Mac.

--
David Empson
dempson@actrix.gen.nz

Re: Leopard compatibility?

In article <1i6fst5.vqx11b140jdf2N%dempson@actrix.gen.nz>,
dempson@actrix.gen.nz (David Empson) wrote:

> manet wrote:
>
> > David Empson wrote:
> >
> > > The computer will still be able to boot Tiger, so there is still a way
> > > to run Classic (or boot Mac OS 9 directly, if the computer is old
> > > enough). I agree that this would be seriously disruptive if you need to
> > > run Leopard and Classic applications at the same time. A second computer
> > > would seem to be a better option.
> >
> > could Parralels or VMware Fusion run both Leopard and Tiger on the same
> > time ?
>
> No. Apple doesn't allow Mac OS X to run in a virtual machine. (I think
> this is a restriction they should relax, as long as it is running on
> Apple hardware.)
>
> Even if it could, it wouldn't help. Parallels and VMware Fusion run on
> Intel Macs, and are virtual machines for hosting an Intel operating
> system.
>
> You can't run Classic on an Intel Mac at all. It requires a PowerPC Mac.

You would probably have to install Mac OS 9 separately and have a
dual-boot system. There are a couple of emulators for running old Mac
software, but as far as I know (and I haven't checked in a while) none
of them handle MacOS 8 or newer.

Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

Re: Leopard compatibility?

Gregory Weston wrote:

> In article <1i6e4tc.4a2keonlltl6N%dempson@actrix.gen.nz>,
> dempson@actrix.gen.nz (David Empson) wrote:
>
> > Also of note: Leopard apparently no longer includes the Classic
> > environment, which means it will not be possible to run FileMaker 5.0 or
> > earlier on Leopard (short of a third-party PowerPC or 68K emulator).
>
> I know I only have to wait 4 days for a definitive answer, but I'd
> really like to see some actual evidence for all the comments about
> Classic going away.

To tidy up that unanswered question: we now have a definitive answer,
straight from Apple:



Mac OS X 10.5 does not support Classic. You therefore won't be able to
run FileMaker Pro 5.0 or earlier on Mac OS X 10.5 (unless you use a
third party Mac emulator, or run the Windows version of FileMaker with
an old version of Windows in a virtual machine on an Intel Mac).

Compatibility between Mac OS X 10.5 and FileMaker Pro 5.5 and later is
as yet unresolved. The main problem might be the web viewer in 8.5 and
9. There was a compatibility issue with the Safari 3 public beta, and
Mac OS X 10.5 comes with Safari 3. If that is the only issue then 5.5
through 8.0 will probably work fine.

--
David Empson
dempson@actrix.gen.nz

Re: Leopard compatibility?

David Empson wrote:

> FileMaker Inc. have published a page on their web site warning that
> FileMaker products may have compatibility issues with Mac OS X 10.5
> "Leopard". They are working on updates for the FileMaker 9 series, but
> the situation is uncertain for earlier versions and there might be no
> official word.
>
>
>
> Just a heads-up at this stage. Don't rush to install Leopard on
> development or production computers.
>
> Does anyone recall similar problems with earlier major updates of Mac OS
> X? I'm able to run FileMaker Pro 6 and 7 on Tiger and I'm not aware of
> any issues they had. I know several people still running versions 6, 7
> and 8.5 who are likely to want to upgrade to Leopard but aren't too keen
> to upgrade to a later version of FileMaker.
>
> Also of note: Leopard apparently no longer includes the Classic
> environment, which means it will not be possible to run FileMaker 5.0 or
> earlier on Leopard (short of a third-party PowerPC or 68K emulator).
>
> This could affect anyone needing to maintain a FileMaker 3 or 4
> database, requiring the use of an older system or another computer.
>
> Anyone maintaining a 5.0 database would need to get hold of 5.5 or 6.0,
> which will run natively on Mac OS X (assuming they are compatibile with
> Leopard).

Seems it's for real this time:

http://docs.info.apple.com/article.html?artnum=303137

Esben

Re: Leopard compatibility?

In article <1i6j94m.1xhet07dh8xxN%dempson@actrix.gen.nz>,
dempson@actrix.gen.nz (David Empson) wrote:

> Gregory Weston wrote:
>
> > In article <1i6e4tc.4a2keonlltl6N%dempson@actrix.gen.nz>,
> > dempson@actrix.gen.nz (David Empson) wrote:
> >
> > > Also of note: Leopard apparently no longer includes the Classic
> > > environment, which means it will not be possible to run FileMaker 5.0 or
> > > earlier on Leopard (short of a third-party PowerPC or 68K emulator).
> >
> > I know I only have to wait 4 days for a definitive answer, but I'd
> > really like to see some actual evidence for all the comments about
> > Classic going away.
>
> To tidy up that unanswered question: we now have a definitive answer,
> straight from Apple:
>
>

Thanks for the link. Would've been nice if that page had been updated
(at the very least) before they took orders.

Back on-topic for FileMaker, over the last few days I've been
investigating MySQL much more seriously than I have in the past. I don't
have faith that older versions of FMP will be reliable on 10.5. I've
already got the most important file I've got loaded, with a front-end
app coming along nicely. Will it ultimately cost me (in time) more than
the $300 upgrade (I'm on v6)? Yeah. But the experiment's worth the time
it'll take.

G

Re: Leopard compatibility?

Do a search in Google for: FileMaker Leopard

FIRST result:

Mac OS X Leopard and FileMaker products
Manage people, projects, assets and more--the easy way.
www.filemaker.com/support/leopard.html - 17k - Cached - Similar pages


click the link to go to FileMaker

FileMaker page result:
We’re sorry, but the page you tried was not found. You may have typed
the address (URL) incorrectly, or the link may be broken. You may find
what you’re looking for in the following links:


Pitiful.

Re: Leopard compatibility?

This works for me today: http://filemaker.com/support/leopard.html

Chris Brown wrote:
>
> Do a search in Google for: FileMaker Leopard
>
> FIRST result:
>
> Mac OS X Leopard and FileMaker products
> Manage people, projects, assets and more--the easy way.
> www.filemaker.com/support/leopard.html - 17k - Cached - Similar pages
>
> click the link to go to FileMaker
>
> FileMaker page result:
> We’re sorry, but the page you tried was not found. You may have typed
> the address (URL) incorrectly, or the link may be broken. You may find
> what you’re looking for in the following links:

Re: Leopard compatibility?

Post removed (X-No-Archive: yes)

Re: Leopard compatibility?

Pretty typical of FMI. Bugs the dickens out of me. I bought 8.5 Advanced
in May and am in no mood to spend to upgrade to 9 after just several
months.

Thank goodness Apple continues to support an "old" OS for at least a few
months after the new one comes out. I guess that if FMI was part of
Apple, we might have hoped for 1-back version support as well.

I've talked with FMI people a number of times over the years.
Increasingly they've given me the strong impression that they aren't
listening to many users. What they haven't really been able to tell me
is who they really do listen to. Bummer.

In article ,
Martin Trautmann wrote:

> On Fri, 26 Oct 2007 08:20:25 -0700, Howard Schlossberg wrote:
> > This works for me today: http://filemaker.com/support/leopard.html
>
>
> As expected:
>
> "We have not tested earlier (pre-FileMaker 9) versions of FileMaker
> software on Mac OS X Leopard and do not intend to release updates for
> earlier versions."

----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

Re: Leopard compatibility?

What limited experimentation I did last night and this morning, FMP6
and FMP7 both seem to work fine under Leopard.


In article , Martin
Trautmann wrote:

> On Fri, 26 Oct 2007 08:20:25 -0700, Howard Schlossberg wrote:
> > This works for me today: http://filemaker.com/support/leopard.html
>
>
> As expected:
>
> "We have not tested earlier (pre-FileMaker 9) versions of FileMaker
> software on Mac OS X Leopard and do not intend to release updates for
> earlier versions."
>
>

Re: Leopard compatibility?

FYI -- the info has been updated at


Howard Schlossberg wrote:
> This works for me today: http://filemaker.com/support/leopard.html
>
> Chris Brown wrote:
>>
>> Do a search in Google for: FileMaker Leopard

Re: Leopard compatibility?

Boo-Pop wrote:

> What limited experimentation I did last night and this morning, FMP6
> and FMP7 both seem to work fine under Leopard.

Thanks for that.
--
Richard Parkin

Re: Leopard compatibility?

Post removed (X-No-Archive: yes)

Re: Leopard compatibility?

Howard Schlossberg wrote:
> FYI -- the info has been updated at
>
>
>
> Howard Schlossberg wrote:
>> This works for me today: http://filemaker.com/support/leopard.html
>>
>> Chris Brown wrote:
>>>
>>> Do a search in Google for: FileMaker Leopard




What really surprises me about this fiasco, is that people do not seem
to be concerned about it. I know my clients most certainly are.


This thread started with raising a relatively minor issue about a
FileMaker page, containing information about the Leopard issues page
reference being lost within FileMaker's own web site. Filemaker's own
site link could not find its own information page on Leopard. I would
consider that very sloppy ; and suggests somebody in FileMaker
responsible for the web site, failed to do some basic checks. Lack of
attention to detail.


Now that there is information out, regarding just what the initial
incompatibility problems are, it seem the lack of checking issue is
again relevant. One might expect that FileMaker had staff assigned to
work with the progressive dev builds of Leopard over the last couple of
years. After all, there is a large community of developers outside Apple
Inc., involved in this way, in testing per-release builds over a
considerable period of time.

Now it seems that:


"Each language version of FileMaker Pro 9 and FileMaker Pro 9 Advanced
works only when the Mac OS System Preference "International Formats
Region" is set to a specific region. For example, the English language
version of FileMaker works only when the region is United States. It
does not work when the region is United Kingdom, or Australia, or
France, or any other region..."

So FM apparently didn't bother to check that other countries could use
the product on their systems. Just another minor oversight.

If you think this is the sort of minor oversight that can occur from
time to time, and that it doesn't affect you, because you have your
system set to US, consider what this appalling lack of fundamental
testing, suggests about the validity of the rest of FM's wider testing
program and procedures. It does not create confidence in a product that
is meant to be about data integrity (and procedural integrity in
handling that data). Of course perhaps too, it is just another example
of American parochialism.


The rest of the English speaking world can use US in the short term and
presumably tolerate the deviations inherent in that. My large base of
medical clients in particular will not be so tolerant, particularly
about spell checking. The French and other languages appear to be out
in the cold. But it is not just language that has been overlooked is it?

IWP does not work
Server deployment does not work 'correctly'. One might interpret failing
to work correctly , for such a pivotal process, as 'it does not work'.


This should be more than just egg on the face embarrassment for
FileMaker, this is another major contribution to perpetuating FileMaker
being seen in many circles as a low level not to be trusted database
system. How long before the jokes start doing the rounds in IT circles?
I would suggest the impact of this incident/fiasco (depending on your
perspective) should not be underestimated. Others no doubt, will wish to
play it down.


It might have been thought that , FM actually were involved in
development testing of Leopard, and possibly that the region
incompatibility, and the incorrect deployment of the server versions,
and the IWP failing to work at all, were just things they either didn't
notice, or just didn't get around to. If FM had actually been involved
in testing with Leopard and were aware of these issues, then it is
interesting that this information was only released after the release of
Leopard. Perhaps there are legitimate business reasons or practices that
would prevent this, or maybe they thought they could get it fixed by the
release deadline, and staff were allocated and working feverishly 24/7
to get it fixed on time. Somehow I doubt it. Maybe they just didn't notice.


I have clients who this year have invested considerable sums of money in
Server 8.5 and FM 8.5 licenses, as well as sever hardware, and even
larger amounts in the development of the database systems to run on
those servers. Now they are going to be forced to upgrade to FM 9 ,
basically within 6 months or so, because they naturally would want to
upgrade their OS to Leopard. Leopard offers substantial reasons from
security perspective to update, apart from feature set changes, and the
individual desire to. My clients are very far from impressed. Their
IT people regard FM as a joke.


As developers, the perception within the client, and the client's IT
support communities, affects the flow of incoming and ongoing business.
Now this, just as FM was starting to gain some potential credence within
IT areas, due to the PHP and SQL carrots, that would not have previously
been prepared to support its adoption.


For those that haven't yet read the update that Howard referenced:

"We have not tested earlier (pre-FileMaker 9) versions of FileMaker
software on Mac OS X Leopard and do not intend to release updates for
earlier versions."


Database systems are ALL about attention to detail. FileMaker has to my
eyes at least, consistently failed to pay sufficient attention to the
detail. The grindingly primitive layout construction handling should be
example enough. Others periodically chorus laments re object triggers
and other missing fundamentals. In their rush to implement features and
functions to capture part of the globalisation market in recent years
via web publishing, and penetrate upscale implementations based on PHP
and SQL interactivity, FileMaker have continued to under-allocate
resources to the basics. This latest fiasco is just another example.
Their stock price, and ongoing adoption rate should reflect this, and
affect us all.





Chris Brown

Re: Leopard compatibility?

Chris Brown wrote:
> Howard Schlossberg wrote:
>> FYI -- the info has been updated at
>>
>>
>>
>> Howard Schlossberg wrote:
>>> This works for me today: http://filemaker.com/support/leopard.html
>>>
>>> Chris Brown wrote:
>>>>
>>>> Do a search in Google for: FileMaker Leopard
>
>
> What really surprises me about this fiasco, is that people do not seem
> to be concerned about it. I know my clients most certainly are.


Chris--

I'm not terrifically concerned because I am a Windows guy and most of my
clients tend to be, as well. But beyond that:

1) On the page at http://filemaker.com/support/leopard.html, they say:
"We are targeting a downloadable update to be available on November 19,
2007." One reason that FMI highly recommends its customers by a
maintenance agreement is so they don't risk missing new features or
compatibility updates. I'm sure that part of their decision to not
update pre-FM9 versions is driven by FMI's marketing department. Their
marketing department has made a lot of selfish decisions that end up
hurting the product's reputation and this may or may not turn out to be
one of them. But how far back in their product line should they go back
to release Leopard updates? Do any of us know how many different fixes
had to be made in FMP9 and FMS9 to make them Leopard compatible? Would
you rather them spend as much time going back to 8.5 and 8.0 to do the
same? Or would you rather them spend resources on field triggering and
"layout construction", as you wish for in your posting?

2) Anyone who jumps any faster than that into a new OS version is
absolutely crazy. As big a Windows user as I am, I still refuse to
install Vista on any of my machines and I don't have one customer who
has even mentioned that they were even thinking about it.

3) If a customer did want to upgrade to either Vista or to Leopard, I
would, as their database consultant, recommend that it would not be a
good idea, that FileMaker may not work 100% properly with it, and that
their other programs may not work 100% properly with it. They could
either take my advice or suffer any potential consequences. That's why
they hire me as their consultant. But IT people would NEVER jump to a
new OS version that fast. No new software is perfect and the IT will
look like the joke when things start going wrong because they wanted to
be first out of the starting gate. That is just not a smart move.

I am often bothered by things that FileMaker, Inc. (FMI) does, but this
is just not one of them. Even though FMI is owned by Apple, they get no
special privileges when it comes to getting advanced codesets. My
understanding is that FM9 has been tested with early versions of
Leopard, but that any software has to go through a series of testing
against the final "gold master" of an OS before it can be certified for
use with that OS. Well, it wasn't all that long ago that Leopard was
set in gold. And then, after certification testing and tweaks, FMI has
to make sure that their Leopard-related changes won't negatively effect
anything else in the code. And then, three weeks later (November 19),
FMI will be able to release an updater to make it fully compatible with
Leopard in all its global languages.

Re: Leopard compatibility?

Hi Howard,



Howard Schlossberg wrote:
> Chris Brown wrote:
>> Howard Schlossberg wrote:
>>> FYI -- the info has been updated at
>>>
>>>
>>>
>>> Howard Schlossberg wrote:
>>>> This works for me today: http://filemaker.com/support/leopard.html
>>>>
>>>> Chris Brown wrote:
>>>>>
>>>>> Do a search in Google for: FileMaker Leopard
>>
>>
>> What really surprises me about this fiasco, is that people do not seem
>> to be concerned about it. I know my clients most certainly are.
>
>
> Chris--
>
> I'm not terrifically concerned because I am a Windows guy and most of my
> clients tend to be, as well. But beyond that:


That is entirely understandable under the circumstances. If this had
happened with Vista, how would one feel about that? Presumptive answer:
hardly surprised. The Apple world is used to stable releases. I have the
majority of my clients as either Mac, or cross platform.



>
> 1) On the page at http://filemaker.com/support/leopard.html, they say:
> "We are targeting a downloadable update to be available on November 19,
> 2007." One reason that FMI highly recommends its customers by a
> maintenance agreement is so they don't risk missing new features or
> compatibility updates. I'm sure that part of their decision to not
> update pre-FM9 versions is driven by FMI's marketing department. Their
> marketing department has made a lot of selfish decisions that end up
> hurting the product's reputation and this may or may not turn out to be
> one of them.

Granted.


But how far back in their product line should they go back
> to release Leopard updates? Do any of us know how many different fixes
> had to be made in FMP9 and FMS9 to make them Leopard compatible? Would
> you rather them spend as much time going back to 8.5 and 8.0 to do the
> same? Or would you rather them spend resources on field triggering and
> "layout construction", as you wish for in your posting?



Normally, I too would see it this way. Software moves on, and
corporations can/could spend inordinate resources on backwards support
that just was not warranted. The client(s) that spends $5000 on FM8.5
earlier this year, and that has a significant proportion of Mac users in
the population, is going to be, and is, more than a little peeved.

Yes I would expect backward compatibility with 8.5, I would in fact
demand it (were it up to me). It is not as if the entire file format has
been changed, a la the MS Word debacle currently. Simplistic perspective
I know; but not supporting the last release: marketing arrogance.


In this case, I do not care how many fixes in FM need to be made, to
produce compatibility, extract the digit FMI, and do it. They would have
had Leopard in test well prior to the release of FM9. Not to get
fundamental language issues addressed for example is just pitiful.

We each have our own preferences and perceptions about shortcomings in
the current release at any point in time. That's normal. System
integration is enormously complex, and resource intensive, that's a
given. If other vendors can generally manage it, why not FM? Deal with
the detail FMI, then fantasize about world domination.

Some things have been on the list of many people preferences for many
years. But that is all a digression. Meant only to raise the point, that
there is long standing list of relatively minor, yet obvious, details
that FMI has chosen to ignore. None of which I would suggest, are
remotely as involved to implement as PHP and SQL compatibilities. Just
an illustration of priorities.



>
> 2) Anyone who jumps any faster than that into a new OS version is
> absolutely crazy. As big a Windows user as I am, I still refuse to
> install Vista on any of my machines and I don't have one customer who
> has even mentioned that they were even thinking about it.

Observing big Windows users over the years, and being cross platform for
many years myself, I thoroughly understand. In the MS world, early
adoption is lunacy. Somewhat different in the Mac Unix world.

The only client I have who was imprudent enough to go Vista, had to
reverse because networking was impossible; this in a large government
hospital environment, and enthusiastic IT. After 5 generations of OSX, I
have yet to see anything like the routine problems the pc side of things
suffer as a matter of course. Locally, universities and hospital systems
have only started to accept XP in the last 2 years for these very
reasons; early adoption, just say no.



>
> 3) If a customer did want to upgrade to either Vista or to Leopard, I
> would, as their database consultant, recommend that it would not be a
> good idea, that FileMaker may not work 100% properly with it, and that
> their other programs may not work 100% properly with it. They could
> either take my advice or suffer any potential consequences. That's why
> they hire me as their consultant. But IT people would NEVER jump to a
> new OS version that fast. No new software is perfect and the IT will
> look like the joke when things start going wrong because they wanted to
> be first out of the starting gate. That is just not a smart move.

I would take the same position, with Vista, and indeed have. I would be
far more relaxed about Leopard; I would normally suggest waiting a month
or so, see what/if anything surfaces, and then make a decision. I would
normally expect there to not be much, if anything at all. Again it is
more than a little different in the non windows world; fear and
justifiable insecurity is just not part of the daily mix.


>
> I am often bothered by things that FileMaker, Inc. (FMI) does, but this
> is just not one of them. Even though FMI is owned by Apple, they get no
> special privileges when it comes to getting advanced codesets.

I will accept your perspective here, but that is contrary to my
casual/outsider based observations of net discussions over the years, of
the interaction Apple has had with other software vendors, and the
feedback from the small army of external interested software developers.
With FMI as an entity under the Apple umbrella, I find it difficult to
accept that the left hand does not know what the right hand is doing.



My
> understanding is that FM9 has been tested with early versions of
> Leopard, but that any software has to go through a series of testing
> against the final "gold master" of an OS before it can be certified for
> use with that OS. Well, it wasn't all that long ago that Leopard was
> set in gold. And then, after certification testing and tweaks, FMI has
> to make sure that their Leopard-related changes won't negatively effect
> anything else in the code. And then, three weeks later (November 19),
> FMI will be able to release an updater to make it fully compatible with
> Leopard in all its global languages.
>
>
>

The initial position of FMI was 'we don't know when a revision will be
forthcoming'. Now that that has been revised, at least for part of the
issue list, many will find that acceptable. Doing what we do, we
understand in some very small way the potential implications of changes,
in a code tree as complex as an OS or app; it is something else again,
granted. But it doesn't work unless the system language is reset to US?
I just don't see that as falling in the 'tweaks' category. That sounds
like an evaluation systems failure to me, that has persisted for more
than just the last weeks of almost master testing.



regards

Chris

Re: Leopard compatibility?

Chris Brown wrote:

> Not to get
> fundamental language issues addressed for example is just pitiful.

I think that langage issues are the last fixes of an OS release...

and, by expreience, foreign issues of MacOSX are frequently bad ones...

non QWERTY issues of MacOS9 had a bug (probably USB implemtation) that
was never fixed and occasionnaly make boot impossible..

so, that FMP, as an Apple sub compagny, have a problem with foreign
versions is not a surprise for me.

foreign versions of FMP 6 had problems with argument separators in
functions (use of ; or ,) that were never fixed.

good foreign developpers have to use US version to work properly
(usualy, user versions works in their final langage...).

--
www.D-L-S.org

Re: Leopard compatibility?

In article ,
Martin Trautmann wrote:

> On Fri, 26 Oct 2007 08:20:25 -0700, Howard Schlossberg wrote:
> > This works for me today: http://filemaker.com/support/leopard.html
>
>
> As expected:
>
> "We have not tested earlier (pre-FileMaker 9) versions of FileMaker
> software on Mac OS X Leopard and do not intend to release updates for
> earlier versions."

Filemaker 7 works quite well with Leopard as tested.

Re: Leopard compatibility?

Lawrence Leichtman wrote:

> In article ,
> Martin Trautmann wrote:
>
> > On Fri, 26 Oct 2007 08:20:25 -0700, Howard Schlossberg wrote:
> > > This works for me today: http://filemaker.com/support/leopard.html
> >
> >
> > As expected:
> >
> > "We have not tested earlier (pre-FileMaker 9) versions of FileMaker
> > software on Mac OS X Leopard and do not intend to release updates for
> > earlier versions."
>
> Filemaker 7 works quite well with Leopard as tested.

My initial testing hasn't found any problems with FileMaker Pro 6 or 7,
but I don't use Instant Web Publishing.

I was specifically testing for the "crash if you speak English but don't
live in the USA" bug.

Another member of my user group told me that FileMaker 8.0 also ran OK
and seemed to not be affected by that particular bug.

It seems this language format setting bug may be limited to 8.5 and 9.0.

Has anyone confirmed it with 8.5, since FileMaker Inc. won't admit to
the existence of older versions?

--
David Empson
dempson@actrix.gen.nz

Re: Leopard compatibility?

How do different versions of FileMaker respond to Leopard?

Here's the information I have for systems running Mac OS X 10.5. It's
based on what my client has told me over the phone. Can you confirm
or add to this information?

FileMaker 8 - FileMaker seems to run fine with Leopard
FileMaker 8.5 - FileMaker will not launch if region is UK or USA
FileMaker 9 - Will not launch if you region is set to UK

Regards
Kevin Smith

Re: Leopard compatibility?

On Oct 29, 8:02 pm, demp...@actrix.gen.nz (David Empson) wrote:
> Lawrence Leichtman wrote:
> > In article ,
> > Martin Trautmann wrote:
>
> > > On Fri, 26 Oct 2007 08:20:25 -0700, Howard Schlossberg wrote:
> > > > This works for me today:http://filemaker.com/support/leopard.html
>
> > > As expected:
>
> > > "We have not tested earlier (pre-FileMaker 9) versions of FileMaker
> > > software on Mac OS XLeopardand do not intend to release updates for
> > > earlier versions."
>
> > Filemaker 7 works quite well withLeopardas tested.
>
> My initial testing hasn't found any problems with FileMaker Pro 6 or 7,
> but I don't use Instant Web Publishing.
>
> I was specifically testing for the "crash if you speak English but don't
> live in the USA" bug.
>
> Another member of my user group told me that FileMaker 8.0 also ran OK
> and seemed to not be affected by that particular bug.
>
> It seems this language format setting bug may be limited to 8.5 and 9.0.
>
> Has anyone confirmed it with 8.5, since FileMaker Inc. won't admit to
> the existence of older versions?
>
> --
> David Empson
> demp...@actrix.gen.nz

David,

I also use 8.0 in a very simple way. Can you get more detailed
information from the member of your user group to make me more
confident about installing Leopard?

Lee
DeaconLee@cox.net

About FM Server 9? Re: Leopard compatibility?

The FileMaker note about Leopard compatibility says that FileMaker
Server 9 won't install in Leopard.

Fine.

But what if you have an existing install of FM Server 9.0v2 running
under 10.4?

Can you *update* this to 10.5 and have the server still function
(assuming you are only serving database files and do not have any of
the web features enabled?)

Anybody try this yet?

- Steve

Re: Leopard compatibility?

manet wrote:

> I think that langage issues are the last fixes of an OS release...

In terms of detail checking, sure.
I would think this is a much lower level switching however. The control
paths/logic flow doesn't change, or does it? The whole program doesn't
require rewriting for UK English? I don't think so, but perhaps it does.
Is the code base rewritten in each and every language? Perhaps working
in US only during dev, speeds processing enough to justify/simplify it
(maybe). Perhaps someone forgot to reset the language switching, i.e.
turn it on.


>
> foreign versions of FMP 6 had problems with argument separators in
> functions (use of ; or ,) that were never fixed.

In English versions one could use either.


>
> good foreign developpers have to use US version to work properly
> (usualy, user versions works in their final langage...).
>


Disregarding the implications of the foregoing, UK English may be
foreign to yourself and FMI, but it is not Mandarin.

Re: Leopard compatibility?

Having no problems with 8.5, but I'm also in the U.S. and haven't tried
the Web server. Things are pretty snappy, too.

Now, a patch for 8.5 would be nice, just in case! I certainly don't want
others to have any problems with the databases we use.

- CSW

Re: Leopard compatibility?

On Oct 30, 11:56 am, donotusethisaddre...@gmail.com wrote:
> How do different versions of FileMaker respond to Leopard?
>
> Here's the information I have for systems running Mac OS X 10.5. It's
> based on what my client has told me over the phone. Can you confirm
> or add to this information?
>
> FileMaker 8 - FileMaker seems to run fine with Leopard
> FileMaker 8.5 - FileMaker will not launch if region is UK or USA
> FileMaker 9 - Will not launch if you region is set to UK
>
> Regards
> Kevin Smith

I installed 10.5 on my MacBook Pro last night, and have been running
8.5 Advanced for several hours. My OS region is USA. I've had no
problems so far. I haven't used IWP, but I'm connecting to remote
files using FMnet without any difficulty. If anyone wants me to test
something in particular, I'd be happy to comply. I'll check this
group.

L Stover

Re: Leopard compatibility?

Post removed (X-No-Archive: yes)

Re: Leopard compatibility?

lansingoogle wrote:

> On Oct 30, 11:56 am, donotusethisaddre...@gmail.com wrote:
> > How do different versions of FileMaker respond to Leopard?
> >
> > Here's the information I have for systems running Mac OS X 10.5. It's
> > based on what my client has told me over the phone. Can you confirm
> > or add to this information?
> >
> > FileMaker 8 - FileMaker seems to run fine with Leopard
> > FileMaker 8.5 - FileMaker will not launch if region is UK or USA
> > FileMaker 9 - Will not launch if you region is set to UK
> >
> > Regards
> > Kevin Smith
>
> I installed 10.5 on my MacBook Pro last night, and have been running
> 8.5 Advanced for several hours. My OS region is USA. I've had no
> problems so far. I haven't used IWP, but I'm connecting to remote
> files using FMnet without any difficulty. If anyone wants me to test
> something in particular, I'd be happy to comply. I'll check this
> group.

I've now confirmed that 8.5 has the "regional settings" bug which also
affects 9.0. These two versions crash on opening a database if running
on Leopard and you haven't set your system region to be US (for the
English version).

I haven't observed this problem with 6.0 or 7.0, and a friend tried 8.0,
which also seemed to be OK (as far as this bug is concerned).

If FileMaker or Apple doesn't do anything to fix this problem, then
English-speaking 8.5 users outside the US are going to be inconvenienced
at least.

This problem is also likely to affect any runtimes created with 8.5 or
9.0, but I haven't confirmed that yet.


--
David Empson
dempson@actrix.gen.nz

Re: Leopard compatibility?

On Oct 31, 9:18 am, Martin Trautmann wrote:
> On Wed, 31 Oct 2007 05:50:21 -0700, lansingoogle wrote:
> > I installed 10.5 on my MacBook Pro last night, and have been running
> > 8.5 Advanced for several hours. My OS region is USA. I've had no
> > problems so far. I haven't used IWP, but I'm connecting to remote
> > files using FMnet without any difficulty. If anyone wants me to test
> > something in particular, I'd be happy to comply. I'll check this
> > group.
>
> Please check printing, both to all of the printers you got and to PDF
> files.
>
> Thanks,
> Martin

Good request - I've discovered that using any of the non-print options
(i.e. Save as PDF, Preview, etc.) in the OS-X print dialog with
Leopard, do not work. There's a pause, but nothing happens. No crash
either.

However, using the Print dialog I can print to my only printer choice,
an HP 9500 inkjet, and it works perfectly. So it seems to be some
conflict with the Leopard Preview application. Not that 'Export as
PDF' works from Filemaker, so it's still possible to generate a PDF
directly.

L. Stover

Re: Leopard compatibility?

CS wrote:
> Having no problems with 8.5, but I'm also in the U.S. and haven't tried
> the Web server. Things are pretty snappy, too.
>
> Now, a patch for 8.5 would be nice, just in case! I certainly don't want
> others to have any problems with the databases we use.
>
> - CSW

CS

a patch will NOT be forthcoming, according to the FM site

http://www.filemaker.com.au/support/leopard.html

"We have not tested earlier (pre-FileMaker 9) versions of FileMaker
software on Mac OS X Leopard and do not intend to release updates for
earlier versions of FileMaker."

Everybody who wants to use Leopard, are forced to upgrade to FM9!




Chris

Re: Leopard compatibility? NOW RELEASED

Chris Brown wrote:
> Howard Schlossberg wrote:
>> FYI -- the info has been updated at
>>
>>
>>
>> Howard Schlossberg wrote:
>>> This works for me today: http://filemaker.com/support/leopard.html
>
> What really surprises me about this fiasco, is that people do not seem
> to be concerned about it. I know my clients most certainly are.

For those who just couldn't wait, there is a new announcement at
. FileMaker has released
FileMaker Pro 9.0v2 and FileMaker Pro 9.0v2 Advanced, available now via
a downloadable update.

The 9.0v2 update provides compatibility with Mac OS X Leopard as
described below, and other features, and is recommended for all users.

Here is a list of other fixes in the 9.0v2 update that developers will
be most interested in:

Mac OS X 10.5 (Leopard):
- The application no longer crashes when creating files if the system
language and region do not match.

General Fixes:

- Mac OS X: Get(SystemVersion) now returns the correct version on Mac OS
X operating systems ending with double digit revision numbers, i.e.
10.4.10.

- The database consistency check initiated on launch will no longer
incorrectly report that a database is damaged for some databases that
can be opened and used without any problems.

- Records will no longer disappear from a portal related to another
portal after approximately 400 records are added.

- Printing Fixes: The update addresses issues which cause the
application to crash when a page range is specified.

- Relationships: A relationship with a global field now returns all
related records if the value of the other key is empty.

- The application no longer freezes when displaying a layout that opens
an external file via a relationship.

For a complete list of fixes please refer to the updater Read Me:
http://www.filemaker.com/downloads/pdf/readme_fmp9v2.pdf

FileMaker Pro 9.0v2 and FileMaker Pro 9.0v2 Advanced Leopard update
downloads: http://www.filemaker.com/support/downloads/index.html

Please note that this update does not fix issues with the FileMaker Pro
9 Instant Web Publishing (IWP) feature running on Leopard. We intend to
make IWP compatible with Leopard in an update expected in December 2007.

We expect to deliver a Leopard compatibility update for our Server
products in early 2008. FileMaker Server 9 and FileMaker Server 9
Advanced currently do not deploy properly on Leopard. In the meantime,
FileMaker Pro 9 and FileMaker Pro 9 Advanced clients running on Leopard
do work with FileMaker Server and Server Advanced running on Tiger or
earlier versions of Mac OS X.

For info on earlier versions of FileMaker software and Mac OS X Leopard:

6702—Updater ReadMe:
http://filemaker.custhelp.com/cgi-bin/filemaker.cfg/php/endu ser/std_adp.php?p_faqid=6702

6703—Article re: older versions of FileMaker running on Leopard:
http://filemaker.custhelp.com/cgi-bin/filemaker.cfg/php/endu ser/std_adp.php?p_faqid=6703

6649—New info on FileMaker products and Leopard:
http://filemaker.custhelp.com/cgi-bin/filemaker.cfg/php/endu ser/std_adp.php?p_faqid=6649

Re: Leopard compatibility?

donotusethisaddressr@gmail.com wrote:
> How do different versions of FileMaker respond to Leopard?

> FileMaker 8.5 - FileMaker will not launch if region is UK or USA

FM 8.5 seems to be working fine for me. There is a delay when starting
and a message about not being able to use web publishing (which I
don't). Local and remote databases seem to work fine. My region is set
to US.

--
Ylan

Re: Leopard compatibility?

Chris Brown wrote:
> CS wrote:
>> Having no problems with 8.5, but I'm also in the U.S. and haven't
>> tried the Web server. Things are pretty snappy, too.
>>
>> Now, a patch for 8.5 would be nice, just in case! I certainly don't
>> want others to have any problems with the databases we use.

> a patch will NOT be forthcoming, according to the FM site

FYI -- FileMaker has now announced via their KnowledgeBase page (answer
ID 6703):

> We have completed limited testing of FileMaker Pro 8.5 running on Leopard and have found some key issues:
>
> 1.
> Region/language issue: On Leopard, each language version of FileMaker Pro 8.5 works only when the Mac OS System Preference "International Formats Region" is set to a specific region. For example, the English language version of FileMaker works only when the region is United States. It does not work when the region is United Kingdom, or Australia, or France, or any other region.
> 2.
> Save to Excel and Export to Excel cause FileMaker Pro 8.5 to hang.
> 3.
> The Instant Web Publishing (IWP) feature does not work.
>
> We plan to provide a software patch to fix the first two issues in FileMaker Pro 8.5 and FileMaker Pro 8.5 Advanced. This patch should be available as a download in December 2007. For timely news on the availability of this patch, please subscribe to FileMaker News, or click the "Notify Me" button below.
>
> The IWP feature in FileMaker Pro 8.5 was designed and implemented long before the Leopard release, and it is not feasible to update it for Leopard.
>
> We hope that fixing these key issues will help affected customers make a smoother transition to FileMaker Pro 9. Please note - there may be other issues with FileMaker Pro 8.5 and FileMaker Pro 8.5 Advanced running on Leopard. These two products will not be supported on Leopard.
>
> Versions of our software earlier than FileMaker Pro 8.5 (8.0 and earlier versions of FileMaker Pro, Pro Advanced, Server and Server Advanced) will not be tested or supported with Leopard. These were developed and initially released years before Leopard became available. We can not update or support these older versions without impacting our support and development of our current product line.
>
> While versions of FileMaker software earlier than 9 may install and run on Leopard, if you do so, you may encounter installation and stability issues for which there is no resolution. We strongly recommend you use current certified software.

Re: Leopard compatibility? NOW RELEASED

Howard Schlossberg wrote:

> For those who just couldn't wait, there is a new announcement at
> . FileMaker has released
> FileMaker Pro 9.0v2 and FileMaker Pro 9.0v2 Advanced, available now via
> a downloadable update.

Excellent. That means I can upgrade to Leopard now. They haven't fixed
Instant Web Publishing yet, but I can live without it. (I don't use
Server.)

(IWP will be fixed in a December update; Server won't be fixed until
early 2008.)

> 6703-Article re: older versions of FileMaker running on Leopard:
> > .php?p_faqid=6703>

I see from this FAQ that they will also be fixing the region bug and
another serious bug (exporting to Excel) in 8.5, but it will be delayed
until December.

They will NOT be fixing Instant Web Publishing in 8.5.

This should be sufficient to allow developers to continue using 8.5 (at
some risk of other bugs as yet unknown) to produce solutions for clients
running Leopard. Anyone dependent on IWP will have to avoid Leopard or
upgrade to version 9.


They won't even be testing 8.0 or earlier, so we'll have to do that
ourselves.

--
David Empson
dempson@actrix.gen.nz

Re: Leopard compatibility?

Howard Schlossberg wrote:
> Chris Brown wrote:
>> CS wrote:
>>> Having no problems with 8.5, but I'm also in the U.S. and haven't
>>> tried the Web server. Things are pretty snappy, too.
>>>
>>> Now, a patch for 8.5 would be nice, just in case! I certainly don't
>>> want others to have any problems with the databases we use.
>
>> a patch will NOT be forthcoming, according to the FM site
>
> FYI -- FileMaker has now announced via their KnowledgeBase page (answer
> ID 6703):
>
>> We have completed limited testing of FileMaker Pro 8.5 running on
>> Leopard and have found some key issues:
>>
>> 1.
>> Region/language issue: On Leopard, each language version of
>> FileMaker Pro 8.5 works only when the Mac OS System Preference
>> "International Formats Region" is set to a specific region. For
>> example, the English language version of FileMaker works only when the
>> region is United States. It does not work when the region is United
>> Kingdom, or Australia, or France, or any other region.
>> 2.
>> Save to Excel and Export to Excel cause FileMaker Pro 8.5 to hang.
>> 3.
>> The Instant Web Publishing (IWP) feature does not work.
>>
>> We plan to provide a software patch to fix the first two issues in
>> FileMaker Pro 8.5 and FileMaker Pro 8.5 Advanced. This patch should be
>> available as a download in December 2007. For timely news on the
>> availability of this patch, please subscribe to FileMaker News, or
>> click the "Notify Me" button below.
>>
>> The IWP feature in FileMaker Pro 8.5 was designed and implemented long
>> before the Leopard release, and it is not feasible to update it for
>> Leopard.
>>
>> We hope that fixing these key issues will help affected customers make
>> a smoother transition to FileMaker Pro 9. Please note - there may be
>> other issues with FileMaker Pro 8.5 and FileMaker Pro 8.5 Advanced
>> running on Leopard. These two products will not be supported on Leopard.
>>
>> Versions of our software earlier than FileMaker Pro 8.5 (8.0 and
>> earlier versions of FileMaker Pro, Pro Advanced, Server and Server
>> Advanced) will not be tested or supported with Leopard. These were
>> developed and initially released years before Leopard became
>> available. We can not update or support these older versions without
>> impacting our support and development of our current product line.
>>
>> While versions of FileMaker software earlier than 9 may install and
>> run on Leopard, if you do so, you may encounter installation and
>> stability issues for which there is no resolution. We strongly
>> recommend you use current certified software.



So within days they have changed their position:
The quote below is still on this page 2.11.2007

http://www.filemaker.com.au/support/leopard.html

"We have not tested earlier (pre-FileMaker 9) versions of FileMaker
software on Mac OS X Leopard and do not intend to release updates for
earlier versions of FileMaker."

Re: Leopard compatibility? NOW RELEASED

Howard Schlossberg wrote:

> Here is a list of other fixes in the 9.0v2 update that developers will
> be most interested in:
>
> Mac OS X 10.5 (Leopard):
> - The application no longer crashes when creating files if the system
> language and region do not match.
>
> General Fixes:
>
> - Mac OS X: Get(SystemVersion) now returns the correct version on Mac OS
> X operating systems ending with double digit revision numbers, i.e.
> 10.4.10.
> p://filemaker.custhelp.com/cgi-bin/filemaker.cfg/php/enduser /std_adp.php?p_faqid=6649
>

and also from other FMI info:

> We have completed limited testing of FileMaker Pro 8.5 running on
Leopard and have found some key issues:
>
> 1.
> Region/language issue: On Leopard, each language version of
FileMaker Pro 8.5 works only when the Mac OS System Preference
"International Formats Region" is set to a specific region. For example,
the English language version of FileMaker works only when the region is
United States. It does not work when the region is United Kingdom, or
Australia, or France, or any other region.
> 2.
....
>
> We plan to provide a software patch to fix the first two issues in
FileMaker Pro 8.5 and FileMaker Pro 8.5 Advanced. This patch should be
available as a download in December 2007.




Someone at FMI found the problem. Good for them.

Re: Leopard compatibility?

Helpful Harry wrote:

> You would probably have to install Mac OS 9 separately and have a
> dual-boot system. There are a couple of emulators for running old Mac
> software, but as far as I know (and I haven't checked in a while) none
> of them handle MacOS 8 or newer.
You are wrong ;-)

Re: Leopard compatibility?

Aladino wrote:

> Helpful Harry wrote:
>
> > You would probably have to install Mac OS 9 separately and have a
> > dual-boot system. There are a couple of emulators for running old Mac
> > software, but as far as I know (and I haven't checked in a while) none
> > of them handle MacOS 8 or newer.
> You are wrong ;-)
>

If you're running Intel you could take af look at COI (Classic-on-Intel)
.. You're more likely to find it in less legitimate places, I'd say, as
it's not yet an official release. The number should be 4.0.1 for the
newest - it can run up to 9.0.4.

Esben

email address not valid

Re: Leopard compatibility?

wrote:

> On Oct 29, 8:02 pm, demp...@actrix.gen.nz (David Empson) wrote:
> > Lawrence Leichtman wrote:
> > > In article ,
> > > Martin Trautmann wrote:
> >
> > > > On Fri, 26 Oct 2007 08:20:25 -0700, Howard Schlossberg wrote:
> > > > > This works for me today:http://filemaker.com/support/leopard.html
> >
> > > > As expected:
> >
> > > > "We have not tested earlier (pre-FileMaker 9) versions of FileMaker
> > > > software on Mac OS XLeopardand do not intend to release updates for
> > > > earlier versions."
> >
> > > Filemaker 7 works quite well withLeopardas tested.
> >
> > My initial testing hasn't found any problems with FileMaker Pro 6 or 7,
> > but I don't use Instant Web Publishing.
> >
> > I was specifically testing for the "crash if you speak English but don't
> > live in the USA" bug.
> >
> > Another member of my user group told me that FileMaker 8.0 also ran OK
> > and seemed to not be affected by that particular bug.
> >
> > It seems this language format setting bug may be limited to 8.5 and 9.0.
> >
> > Has anyone confirmed it with 8.5, since FileMaker Inc. won't admit to
> > the existence of older versions?
>
> David,
>
> I also use 8.0 in a very simple way. Can you get more detailed
> information from the member of your user group to make me more
> confident about installing Leopard?

Hi Lee

I've now had independent confirmation from a local FileMaker developer
that version 8.0 is not affected by the regional settings bug with
Leopard. That problem is limited to versions 8.5v1 and 9.0v1. (9.0v2 is
already available, which has fixed that bug.)

There are other problems with version 8.5 which may also affect 8.0:

Inability to export to Excel.
Instant Web Publishing doesn't work.

I have direct or easy access to all versions of FileMaker Pro from 5.5
to 9.0 _except_ 8.0 so I can't test that specific version but I am
trying all the others as time permits. I'm only running Leopard
occasionally on my main computer, until my most important applications
have been updated for compatibility (and I still have several utilities
to go).

--
David Empson
dempson@actrix.gen.nz

Re: Leopard compatibility?

Ylan Segal wrote:
> donotusethisaddressr@gmail.com wrote:
>> How do different versions of FileMaker respond to Leopard?
>
>> FileMaker 8.5 - FileMaker will not launch if region is UK or USA
>
> FM 8.5 seems to be working fine for me. There is a delay when starting
> and a message about not being able to use web publishing (which I
> don't). Local and remote databases seem to work fine. My region is set
> to US.

Scratch that. I have problems exporting to Excel. I just hangs forever.

Exporting to CVS works, so I am using that as a workaround.

--
Ylan.

Re: Leopard compatibility?

Ylan Segal wrote:

> Ylan Segal wrote:
> > donotusethisaddressr@gmail.com wrote:
> >> How do different versions of FileMaker respond to Leopard?
> >
> >> FileMaker 8.5 - FileMaker will not launch if region is UK or USA
> >
> > FM 8.5 seems to be working fine for me. There is a delay when starting
> > and a message about not being able to use web publishing (which I
> > don't). Local and remote databases seem to work fine. My region is set
> > to US.
>
> Scratch that. I have problems exporting to Excel. I just hangs forever.

Known issue with 8.5 and Leopard, and FileMaker Inc have said they will
be fixing that one (in December) along with the regional settings
problem. They won't be fixing Instant Web Publising for 8.5.

> Exporting to CVS works, so I am using that as a workaround.


--
David Empson
dempson@actrix.gen.nz

Re: Leopard compatibility?

On Nov 5, 2:04 am, demp...@actrix.gen.nz (David Empson) wrote:
> wrote:
> > On Oct 29, 8:02 pm, demp...@actrix.gen.nz (David Empson) wrote:
> > > Lawrence Leichtman wrote:
> > > > In article ,
> > > > Martin Trautmann wrote:
>
> > > > > On Fri, 26 Oct 2007 08:20:25 -0700, Howard Schlossberg wrote:
> > > > > > This works for me today:http://filemaker.com/support/leopard.html
>
> > > > > As expected:
>
> > > > > "We have not tested earlier (pre-FileMaker9) versions ofFileMaker
> > > > > software on Mac OS XLeopardand do not intend to release updates for
> > > > > earlier versions."
>
> > > >Filemaker7 works quite well withLeopardas tested.
>
> > > My initial testing hasn't found any problems withFileMakerPro 6 or 7,
> > > but I don't use Instant Web Publishing.
>
> > > I was specifically testing for the "crash if you speak English but don't
> > > live in the USA" bug.
>
> > > Another member of my user group told me thatFileMaker8.0also ran OK
> > > and seemed to not be affected by that particular bug.
>
> > > It seems this language format setting bug may be limited to 8.5 and 9.0.
>
> > > Has anyone confirmed it with 8.5, sinceFileMakerInc. won't admit to
> > > the existence of older versions?
>
> > David,
>
> > I also use8.0in a very simple way. Can you get more detailed
> > information from the member of your user group to make me more
> > confident about installing Leopard?
>
> Hi Lee
>
> I've now had independent confirmation from a localFileMakerdeveloper
> that version8.0is not affected by the regional settings bug with
> Leopard. That problem is limited to versions 8.5v1 and 9.0v1. (9.0v2 is
> already available, which has fixed that bug.)
>
> There are other problems with version 8.5 which may also affect8.0:
>
> Inability to export to Excel.
> Instant Web Publishing doesn't work.
>
> I have direct or easy access to all versions ofFileMakerPro from 5.5
> to 9.0 _except_8.0so I can't test that specific version but I am
> trying all the others as time permits. I'm only running Leopard
> occasionally on my main computer, until my most important applications
> have been updated for compatibility (and I still have several utilities
> to go).
>
> --
> David Empson
> demp...@actrix.gen.nz

I'm running 8.0.3 with Leopard with no problem.