asp pages and filemaker server

[Richard Stolk]

Dear All,

I want to use the data from a filemaker 5.5 SERVER in an ASP(x) page (through ODBC or Fmconnetor) Until now it seems that all filemaker files have to be open through some sort of client also needed to be installed on the server.

It is unaceptable for our organisation to have a NT server logged on and/or a (client) application open on a server.

does anyone know if my statments and finding are correct.

if all is true does anyone have a workaround?

thanks in advance

regards

Richard Stolk

[Garry Claridge]

FM needs to be open on something, not usually on your Server.

I haven't had much luck getting ASP to talk directly to the WebCompanion. I use PHP, some people have used Perl. However, I'm sure somebody will have an ASP solution, maybe just ODBC or XML.

Good Luck.

Garry

[Leb i Sol]

to sum it up:

-FM will run almost any platform (Linux, win server or station, Mac)

-there are many posts about this issue....

-ODBC is NOT the way to go.(security (FM needs remote web anabled) +performance is about 0.9 on a scale 1-10)

-ASP+XML seems to be working quite well for some people arround here...do a serach on web related forums u will find more info...

[Richard Stolk]

Maybe it's me; but isn't it very strange you need a client running in order to access data in the database :

(I understand the server is not the place to run this client but, I really even don't want a workstation "somewhere" open and running 24 hr's a day)

OR

is as you described XML the way to go ?

If we use XML does this eliminate the need to have

this "client" running "somewhere" ?

OR

would a workaround be to run filemaker as a service ?

and if so does anyone have the command line parameters to

enable remote access end sharing ?

hope someone can help

thanks in advance

best regards

Richard

[Unable]

Perhaps the real problem is attitudinal, specifically, "It is unaceptable for our organisation ..."

Sounds like a vhin ordinaire (a common whine) is being served here.

FMPro is quite flexible, but, like all tools, has its environmental limitations and restrictions of use. For instance, an electric saw is a great tool - as long as the restriction of the availibility of electricity is met. Your organisation may need to recognize the environment and adapt accordingly.

Otherwise, if FMPro truly is not acceptable ..., then spend $50k or more on something that will be acceptable to the organisation.

[Garry Claridge]

FM does need to run somewhere for all access. Most other database systems also need to be running for access. (MS Access does not appear to need to "run" because the DB engine is built into the Jet Drivers called by the ODBC.)

FM Server can run as a service.

All the best.

Garry

[Mariano Peterson]

FileMaker Server must be running in order to retrieve data using a FileMaker Pro client. Unfortunately, HTTP and ODBC requests can only be handled by FileMaker Pro, and not FileMaker Server. FileMaker Pro works within a user context, so in order to use FileMaker Pro as a data provider for HTTP and ODBC you must have a client copy of FileMaker Pro running on a logged in computer on the network. Yes, this means you must leave a work station or server logged in 24x7... and yes, that is highly undesirable.

I've heard of people creating their own services based on the FileMaker Pro client application, enabling them to use FM Pro as an HTTP and/or ODBC data source while the computer is not logged in - in essence, allowing FileMaker Pro to run independent of a user context. I've not had any luck with this, but have not bothered to pursue it much either. Here is a link posted by somebody who seems to have succeeded in this regard:

http://www.sudde.no-ip.org/fmpservice.html

Hope this helps,

Mariano