I recently showed a small company a small FMP 7.0 solution of mine and now they want both FMP and my solution...

Unfortunately I'm on a Mac OS 10.3.9 (single user) and they're on a (small) multiple-user Windows network...

1) Do they need to get, say, FMPro 1-5 user license.

2) Should they then get FM Server too?

With regards to my solution, would anybody expect major problems between my Mac solution and their Windows network?

All help and advice will be gratefully received.

Tim

They can order a volume license including Server from FileMaker UK.

There are a few cross-platform issues including font appearances and some platform specific steps in ScriptMaker, but generally you are Ok cross-platform.

HTH

Steven

Tim:

They may not need FMServer - it depends on how intense their usage requirements will be. Otherwise, Steven's advice is perfectly sound; you've got to have a good look at the system on Windows in order to make sure your layouts look decent, and also to make sure that you're not having any font-substitution issues, and hopefully you're not using AppleScript, which obviously doesn't work on Windows.

-Stanley

Hi Tim,

Each workstation will need a separate license. If they have more than 10 workstations, they will benefit from a volume license deal (contact filemaker directly for this.)

The client version can host up to 5 concurrent connections, so if they have more than 5 workstations, you should recommend Server for hosting. In general, hosting with Server is better for its performance and scheduled backup abilities.

There are several things you'll need to check/fix for a solution in the situation you described.

First, going from Mac to Windows has some issues, including differences with font spacing, OS level scripting, print/page setup, and window zooming and positioning.

Second, going to a multi-user database introduces issues with record locking that would not have been a problem in a stand-alone database. Also, you have to account for the way globals hold their values in a hosted solution.

Thank you all for your comments. Generally speaking your combined thinking hasn't terrified me, but, needless to say, you have raised a few more specific queries in my mind; moreso because I'm a 'network' virgin...

If they've got 5 work-stations and a server they could purchase the 1-5 user client version? [Not necessarily committing to the additional bonuses offered by the Server edition]

Would I be right in thinking that structurally FMP would be loaded on to each work-station whilst my solution would reside on the server?

If they've got 6 work-stations but don't anticipate more than, say, 4 stations running FMP simultaneously, can they install the 1-5 client across all 6 stations or does that not work?

Stanley, how do you quantify "...how intense their usage requirements will be..."?

"The client version can host up to 5 concurrent connections"

"... going to a multi-user database introduces issues with record locking that would not have been a problem in a stand-alone database"

Given that I don't have a grasp of networking, what's being said here, and please correct me if I'm wrong, is that my solution can be accessed simultaneously by 5 users? So 5 people can create and edit records...How does anything get saved?

In terms of cross-platform comments, Steven's "...and some platform specific steps in ScriptMaker...", and "you have to account for the way globals hold their values in a hosted solution" are the greatest concerns. Can you point me to where I might find these minefields explained in detail?

Thank you again. You've already helped no end - though admittedly, whilst one cloud of confusion has left, another has taken it's place!

Tim

Tim:

If you're going to only have 5 or 6 total users, then I'd say you could surely go without FM Server, and have the solution hosted by a machine running FMP. However, you will have to buy a license for each machine, unless you choose to enable IWP (Instant Web Publishing) to allow users to access the db via their web browsers. But that's a whole 'nother can of worms.

As far as the platform-specific stuff, really it's mostly the things already mentioned, especially the different ways Win/Mac handle fonts and printing.

Globals. Globals are client-specific, and revert to original values each time the solution is opened by a user.

Much of this stuff is explained in great detail in the Best Practices white paper on FMI's web site at:

http://www.filemaker.com/downloads/pdf/fms_best_practices.pdf

Other FMI white papers can be found at:

http://www.filemaker.com/support/whitepapers.html

-Stanley

Globals are user and session specific; that's why they are valuable. In FileMaker Pro 8 variables can replace globals in many instances, although not all.

Steven

Actually the break-even point on license costs of vLA vrs. FGU (finished good unit aka FMP in the box) is at 6.5 seats, IIRC. IOW, it's less expensive to purchase a 10 seat VLA than it is to purchase 7 FGU's.

YMMV by country and if there are special deals afoot.

HTH

Steven

The decision to ue FileMaker Server should not be based on number of users alone, although clearly there is a maximum threshhold for peer-to-peer connections.

Speed, safety, automated backups, server side calculation resolution, External Server Authentication (with or without Active Direcory or Open Directory)--all these argue strongly for FileMaker Server.

I have actually had 2 different clients who had only ONE user, but insisted on FileMaker Server because of the safety issues.

HTH

Steven

Thanks again to all of you for your advice. I now feel educated enough to recommend FMP whilst gently suggesting that they additionally invest in the Server edition.

And I am fully fore-warned as to which bits of my Mac construct are most likely to fall apart when placed anywhere near a PC!

I hope you guys are all around to answer whatever my next questions may be!

Cheers

Tim