I've developed a job bag system for design agencies that I would like to package and sell. I will be writing manuals and the like shortly, but I need a solution that is stand alone and doesn't require the purchase of Filemaker by the end user. The system needs to run as client/server setup. I have an idea that this will require that each installation will require filemaker server, and then the runtime version of the system that acesses the published databases accross the network on each host machine. Is this correct, what are the pitfalls?

Many thanks for any help or advice.

Regards

Kevin Price-Ward

Runtime is NOT networkable.

Just bundle the necessary licenses for Filemaker within your system. Filemaker has a special setup just for this purpose. However you are absorbing the support costs.

When I did this, we just facilitated the purchase of the necessary hardware (i.e. the server) and software (i.e. the VLA/Filemaker Server) by the client. This then gives them full support from Filemaker, then we installed everything as part of the purchase of our system.

Arrrgh, 'runtime is not networkable'!!! - that sucks. I really need the ability to be able to stop people from switching between databases via the 'window', menu option and I need the application to have the appearance of being a single window, rather than a whole load of linked databases just positioned in the exact same position on top of one another, question is how, if I can't use the developer edition?

Kevin

Try using Plugins for your solution.

I suggest you use Dacons Menu Control. It will create a "virtual menu" and replace filemaker menus with the one's you've created. It cost around $90 single user. go to www.dacons.net

Or try using WindowUtility plug-in. You can hide windows, set window position,move window, change window caption and a lot more!

Try searching the plug-in at www.fmplugins.com

Plugins are cheaper than FM Developer, and networkable.

Website for the WindowUtility plugin => http://www.medeyedbs.com/plugins.html

it cost $200

Arrrgh, 'runtime is not networkable'!!! - that sucks.

Why? FMI need to have income. What is the point in selling Developer version for less than $1000 and then loose sale on 100 or 10 000 licenses?

I really need the ability to be able to stop people from switching between databases via the 'window', menu option

If all databases are always "parked" in blank window with single button "Menu" I see no problem with that.

Just want to ask is that runtime totally cannot support network function even only have less than 10 user.

Let say if i have 8 user and 1 server in a network, can i just buy a install a FM server for the server system and then user runtime version for the client systems, is that work? Or neet to install a FM server for srver system and also install FM Pro for every client system?

Regards

Henry

Thanks for the input, I am going to check out the plug-ins that you mention.

Henry, I think the general concensus of opinion is that runtime is not networkable - full stop.

Anatoli, what do you mean by 'parked in a blank window?' is this some trick that I don't know about?

Many thanks

Kevin

You open the database and in start script you'll go to blank (white) layout. Lock also the left status area.

Put single button on that layout with script "Main Menu".

That is all. You can use anything from that database and users are locked away.

If you will call something in such database, you will send user to some nice layout, and after finishing their task, they will be switched again to blank layout and the database will be minimized.

HTH