jbschwartz

On first examination, the code looks ok, but recreating the query reveals that "newFindAnyCommand" doesn't produce a result for Summary fields. It also doesn't make sense to find just one record and then add an additional FindCriterion. Suggest using "newFindCommand" instead. For what is worth, I have always just generated summary totals on the fly during foreach loops, like this: $records = $result->getRecords(); foreach ($records as $record) { $totalSales = $totalSales + $record->getField("Sales"); } echo $totalSales; Hope that help

I did one of these last year and had similar issues. Migrating from FMS 10 to FMS 16 involves upgrading not only FMS, but PHP and Windows as well. Lots of little things to go wrong but no fundamental hurdles Heres what I remember: - Adjust IIS security settings to be able to see the actual error vs the useless 500 page. Or perform the operation from the server directly with full PHP error reporting - Eliminate PHP short tags - Look for date format handling conflicts. The solution I worked on had an automated logging routine that attempted to write a date in the wrong

Please visit the FMS Custom Web Publishing Test page to confirm that the server is working properly.

Aussie John, Not sure if the single quotes you are using are "legal." I just tried the code on my local machine and got a syntax error... another source of seeing a black page. To be sure, change all to double quotes. When I did that, the page did run but returned a different error but I'm not running the current PHP API on my local development machine. What do you get? I

Try this: $records = $result->getRecords(); $record = $records[0]; $name = $record->getField("Name"); $color = $record->getField("Favorite Color"); echo $name.’ - ‘. $color;

Aussie John: Based on your code, it SHOULD be blank. You are only echoing a result if there is an error. What do want to do with the found record?

There are slew of them, depending on whether you have a one machine or two machine installation, and what version of FMS we're talking about. See this page to pick your FMS version. https://support.filemaker.com/s/answerview?language=en_US&anum=14402 Hope that helps.

Error 22 in CWP is the catchall for a failed connection between the API and FMS. Although the message mentions username and password as potential causes, the list is much broader than that. For perspective, I wrestle with Error 22 on nearly every new project until all the settings are tweaked. One setting that I don’t believe I saw mentioned...have you opened the required ports on the server firewall?

This is what Custom Web Publishing (CWP) is for using the PHP API. In short, web pages in your main company website can be outfitted with php code to offer the search form you desire, the ability to query your FMP database and return data in the format you desire. Every FMS system since version 7 offers this capability. It provides a “normal” web experience for your end user. That’s the good news. The hurdle of using CWP is mastering the full stack of tools that are involved: HTML, CSS, PHP, the PHP API, Apache/IIS, and probably JavaScript, JQuery, AJAX , BootStrap... and more... too muc

Joost, I don't believe that there is anything to do on FMS or Apache itself. But in php, provide the full LOCAL path to the new pictures folder location. In this example, I'm setting up a DEFINE in the config file to the pictures folder relocated to an external hard drive: define('PICTURES', '/Volumes/Your_External_Hard_Drive_Name/pictures/'); You might need to experiment with the permissions on the pictures folder and/or the hard drive so that fmserver/apache/php can access. BTW...This answer is assuming that you are storing the images directly in a folder and using html/

Tony, This looks like code generated by SiteAssistant...which was a flawed concept from the start. But we won't go there. Going back to the $result you posted, I realized that it's not returning any results. Everything up to the last 5 lines is normal. but the last 5 lines represent arrays (layout, records, etc) and is supposed to be populated with literally hundreds/thousands lines of data. Can't expect the record link functions to work without having data to work with. Is this system online? I can try and resolve from here.

Tony, Looks like you received a valid result from the query. I assume that there was more to the result other than what you posted. Moving forward, what happens after this?

A number of things come to mind: 1) Updating the machine (probably) involves updating to a new php versions and IIS, either of which could be playing a part in the failure. Come back to that later after #2. 2) I would want to know what $result FMP Server is reporting after any query. Try adding print_r($result); exit; after the query to see how FMP is responding.. Hope that helps. Jonathan