Logon, su to ldm (sudo su - ldm) and run:
ldmadmin start
If the queue is corrupt, the LDM will freak. In this case,
do the following:
ldmadmin stop
ldmadmin delqueue
ldmadmin mkqueue
ldmadmin start
It's good to run: ldmadmin watch after that, just to verify that stuff is coming in.

“I have installed fetchmailconf 6.3.9~rc2-4ubuntu1 on Ubuntu 9.04; /usr/bin/fetchmailconf — a shell script to start the real Python script — fails to start because it looks for the real fetchmailconf script in the wrong place.”

Share this:

I would STRONGLY urge you to ditch Claris Homepage and Filemaker for a more robust solution. If you still insist on using them, this should at least get you started…

Instructions for using Claris Homepage 3.0 to create forms for Filemaker Pro 4.0

1> Make sure that FM Pro 4.0 is running and that the desired database is open and shared.

2> Start Homepage and goto — File: New…

3> Choose “Use Assistant”

4> Choose Filemaker Connection Assistant.

5> Follow the Assistant through.

IMPORTANT NOTES ABOUT THE CONNECTION ASSISTANT

On the Database Selection Screen …

DON’T US “This computer”. It’ll kill CHP, or lock up the computer, OR BOTH. I’ve NEVER gotten it to work successfully.

USE: IP Address= localhost, and then click “Connect to server” button. This should bring up a listing of any open and shared databases.

Layout Selection: Make sure that the layout that you select contains all of the fields that you want to be able to use on your form, because you will select the specific fields used a couple of steps down the road.

Feature Selection: You can select to create both the Search and Add New Records pages at the same time here.

Location: I generally choose to create a New Folder to keep all of the pages together, so that I can easily find them to tweak ‘em to my liking. Also, the possibility exists that there may be other files of the same name that would be overwritten otherwise.

The submission form can be created directly as a web document, or can be converted from a word-processing document. Either way, you will probably have to do a fair amount of formatting. You will need to arrange the answer choices in some type of a consistent, useful manner, most likely through the use of tables. You will also need to determine whether the answer will be “Choose One” (radio buttons), “Mark All That Apply” (checkboxes), “Fill in the Blank” (text field), or “Short Answer” (text box). Go ahead and layout the answers and insert the appropriate form objects at this point. In a couple of steps we are going to be determining field names and values and it is easier to ensure that ALL of the necessary fields and values have been determined if we can note all of the names and values in the appropriate places on a hardcopy.

2> Print out the new/converted submission form.

Print the submission form out so that the field names and values can be written directly on a hardcopy.

3> Determine database field names and values for each entry on the form and write them on the printout.

Once all of the names and values are determined, the hardcopy will be used when entering field names in the new database.

4> Create the database.

Start FileMaker Pro and go to File:New Database. Enter the name and save it in the appropriate location. For OIS databases, they are saved in the FileMaker Pro 4.0:databases folder on the OIS Server.

5> Enter the field names.

Once it is saved, go ahead and enter all of the necessary fields. Most of the time the fields can be left as “Text”. Once you have finished adding fields, click “done”. You will also need to set the new database to be available online. Go to File:Sharing…. and click on the box next to Web Companion. That is all that needs to be done to prepare the database.

6> Modify the submission form to include the field names EXACTLY as they exist in the database.

Return to the Submission form and add the field names and values to all of the appropriate form objects. A WORD OF CAUTION! – After you’re done entering them, double-check them. Even have someone else double-check them. As the form grows to over a dozen or so radio buttons, checkboxes, etc. it becomes almost a given that at least one will have a misspelled or incorrect field name or value.

7> Add the required FileMaker Form tags.

Since we will be using FileMaker to process the information in the form, we need to add the appropriate tags to the Submission page to allow FileMaker to work correctly. The easiest way to ensure that we have all of the appropriate tags is to use the FileMaker Form Library within Homepage 3.0.

Share this:

(Now Includes FMP 5 Error Codes)PLEASE NOTE: I don’t use Filemaker anymore, but this page is popular enough that I’m going to try to improve it and make it more useful.
I would encourage you to look into using PHP and MySQL in place of Filemaker.

5 Command is invalid (for example, a Set Field script step does not have a calculation specified).

100 File is missing.

101 Record is missing.

102 Field is missing. (In my experience, a field name in the form was usually misspelled, so Filemaker didn’t recognize it. In any event, the form is sending Filemaker a field name or names that Filemaker isn’t finding in the database.).

103 Relationship is missing.

104 Script is missing.

105 Layout is missing.

200 Record access is denied.

201 Field cannot be modified.

202 Field access is denied.

203 No records in file to print or password doesn’t allow print access.

204 No access to field(s) in sort order.

205 Cannot create new records; import will overwrite existing data.

300 The file is locked or in use.

301 Record is in use by another user.

302 Script definitions are in use by another user.

303 Paper size is in use by another user.

304 Password definitions are in use by another user.

305 Relationship or value list definitions are locked by another user.

306 Record modification ID does not match.

400 Find criteria is empty.

401 No records match the request.

402 Not a match field for a lookup.

403 Exceeding maximum record limit for demo.

404 Sort order is invalid.

405 Number of records specified exceeds number of records that can be omitted.

406 Replace/Reserialize criteria is invalid.

407 One or both key fields are missing (invalid relation).

408 Specified field has inappropriate data type for this operation.

409 Import order is invalid.

410 Export order is invalid.

411 Cannot perform delete because related records cannot be deleted.

412 Wrong version of FileMaker Pro used to recover file.

500 Date value does not meet validation entry options.

501 Time value does not meet validation entry options.

502 Number value does not meet validation entry options.

503 Value in field does not meet range validation entry options.

504 Value in field does not meet unique value validation entry options.

505 Value in field failed existing value validation test.

506 Value in field is not a member value of the validation entry option value list.