FMPro 5.5 and CDML

[BrizUK]

Have been running FMPro 4.1 on the web and using CDML to search and display results. This has been running for four years with no problems on our own server running Mac OS 8.6. For various reasons have now changed to FMPro 5.5 using a third party server also running Mac OS 8.6.

Using the same CDML based pages the database file cannot be accessed and an error message stating File Not Found with the subtext 'The file you have requested does not exist on the server'

Despite checking all coding and the parameters for Web Companion etc cannot solve the problem. HAs anyone any ideas as to what may be the reason.

[Unable]

Did you edit the format files so that db.fp3 is now db.fp5?

[BrizUK]

Thanks for the suggestion Unable but the reference was changed to db.fp5 Other than that all the CDML is identical to that used when the system worked in 4.1

[Garry Claridge]

Double check the "Sharing" for each database.

Good Luck.

Garry

[BrizUK]

Thanks Garry but that isn't the problem either. I am coming to the conclusion that the problem is with our ISP's server and nothing to do with our code or our database. But proving it is going to be difficult.

[Steve T.]

Howdy... Actually, if you switch servers, your pages MIGHT have to be changed, especially wrt to things like paths and FORM ACTIONS. We had problems w/FM4 not understanding subdirectories when stated in the FORM ACTION... everything had to be relative to root. We had to do

<form action = "http://www.ourdomain.com/FMPro"> or "FMPro" and not

<form action = "http://www.ourdomain.com/subdirectory/FMPro" method = "post">

--In your case, is it possible that your solutions were designed for root but your ISP puts your stuff in a subdirectory of root?

FileMaker 5.5 > Web > accountname > index.html

--Or are you the only FM user and they give you the root exclusively?

--Have you tried accesssing them via Instant Web Publishing just to see if you can?

Just throwin' it out there since you're fishin'.

--ST

[BrizUK]

Hi Steve - Yes, I am in a subdirectory. My form action was originally <form action="FMPro' method="post"> Removing the "post " statement as you suggested got the search parameters up in the address line which I didn't get before but I still can't get the database. Also tried your suggestion of Instant Web Publishing using the built in home page but that still gives me a 'file not found' message.

Have been trying to find out from our ISP exactly what the subdirectory setup is to see if that helps. They have other users on the server who must have solved the problem but the ISP support people I have talked to don't seem to know the answer!!

[Garry Claridge]

You could send a copy of the file to somebody else to setup so that you can check remote CDML access. I could even set it up here.

This would then put the onus back on the ISP/Hosting Service to solve the problem.

All the best.

Garry

[Steve T.]

Ah, sorry.. I'm a dufus and did not mean to leave out the method="post" although that will default to method="get" and show you your URL string. I just meant if your solutions were designed for root, you may have to change your forms to account for the subdirectory change.

If you want to see if IWP works, here is the URL if an IWP-published db (copy/paste from my terminal)..

http: (spacefornourl) //mydomainandport.com/FMRes/FMPJS?-db=test.fp5&-layID=1&-token=25&

-max=1&-format=formvwcss.htm&-mode=browse&-findall

Change the mydomainandport.com and -db=test.fp5 parts to match yours and see if anything comes up. If nothing comes up, this is not helpful. If something does come up, at least we know your db is properly shared and you can try to narrow it down to directories and/or permissions. Oh, yeah... permissions can make a file look like it's not there, too. If only YOU can read them, a web browser will not see them.

Just a couple more things to try...

--ST

[BrizUK]

Thanks to everyone who has been giving me possible solutions to my problem, all of which have reinforced my faith in the FMPro community.

The issue has been solved. After a final rather blunt email to my ISP they have now confirmed that they had set up the server incorrectly! What an admission but better late than never, I suppose. So there was nothng wrong with my coding or setup of my db.fp5 files.

Thanks again everyone.