chandra
-
Posts
27 -
Joined
-
Last visited
chandra's Achievements
-
quote: Originally posted by Vaughan: What's a meta refresh? Can you post the html code that makes this powerful magic happen? The <meta> tag goes into a HTML in the <head> section. Here's the format: <meta http-equiv="Refresh" content="Value"> "Value" can be an integer of the number of seconds before the browser reloads the same document. For example, <meta http-equiv="Refresh" content="5"> would reload the HTML document every 5 seconds. The <meta> refresh can also be used to re-direct a browser to a new URL by including an absolute URL to the "Value". For example: <meta http-equiv="Refresh" content="5; URL=http://some_new_url.com/home.html"> After displaying the current document (where the <meta> tag is) for 5 seconds, go retrieve home.html from the some_new_url.com web server.
-
I think I ran into a similar problem. I ended up creating separate layouts in FM Pro. One for new record input, and one for edit record input. Try taking out the :related fields in your "new record" -layout.
-
Quote from Techinfo Article 104764 ( http://www.filemaker.com/support/techinfo.html ) quote: CDML: Using the Return or Enter Key to Submit a Browser Form Visitors submitting a form via browser often hit the Return or Enter key instead of clicking on a Submit or Search button. However, the two actions do not always submit the same information. This is a function of the way HTML works currently, and is not a limitation of Claris Home Page 3.0 or FileMaker Pro 4.0. To ensure that a form is correctly submitted when a visitor presses Enter or Return, add a hidden input type to your form, attaching the same name to it as your Submit button. For example, the HTML for your submit button in a search page might look something like this: <INPUT TYPE =
-
I believe all you have to do is add a -mailto line for each address you wish to send to. Don't forget there is also the -mailcc and -mailbcc tags too... I personally haven't gotten the mail feature to work (I tried it for fun ) Luckily, I don't need it for my application
-
New record not displaying some info...
chandra replied to chandra's topic in Other Internet Technologies
This is a just an addendum note to say that the problem with the ID field not showing has been fixed using a <meta> refresh. However, the related field, info still doesn't pop up until I click on the "Update" (-edit) button. I tried changing my -script to -script.prefind and -script.presort and for some reason or other, it seemed not to run at all (the script itself is only one line, SetField) as my ID came out completely blank. [This message has been edited by chandra (edited September 01, 2000).] -
quote: Originally posted by yafreax: i don't know if anyone else has ever had this problem, but unless i use a meta refresh, none of my pop-up menus work. if i refresh the page it works fine. I'm not sure why, but this happens with everysingle one of my Pop-ups! Oh well, it's a pretty easy fix that you might want to try. by the way, if anyone knows why this happens or how it's fixed, let me know. The refresh is fine, i'm just curious as to what's going on and if anyone has experienced the same thing. I have not had this problem. I assume you are talking about the form element <select> when you talk about pop-up menus? I am just curious, what do you mean when you say they "don't work"? Is it that they are not there, or that they are there, but the pop-up menu is empty?
-
I have a web form which, when completed and submitted (-new), loads another html page which confirms the record was created successfully and displays the contents of the new record to review and edit in case of data entry error. My problem is that the field where the ID number for the record, which is generated via a script, is blank. Currently my two work arounds are: a) immediately click on the "Update" (-edit) button, which saves and re-loads the same record, and take out the display of the record and provide a link (ie. click [HERE] to review the record) in the confirmation message. A similar problem occurs in the fields where I am showing information from a related record. Is there a way of immediately displaying this information without having to do the above work arounds? Please post any suggestions, or if I was unclear in my post, any clarifying questions. Thanks! [This message has been edited by chandra (edited August 31, 2000).]
-
Could you post the HTML code you used in your format file as well as how the Browser interprets the code? ie. post the HTML source from the format file AND the HTML source from "View Source" within your browser. Another thing you could try in the interim (learn to walk before you run ) is to create a simple value list in your main file and see if you can get it to display properly on your web page. This might help you troubleshooot your the related-field value list problem. This is a direct copy/paste from the CDML Reference.fp3 that comes with FM Pro 4.1 quote: Syntax example(s) Display value List using an HTML file [FMP-ValueList: Groups, List=GroupList] <input type="radio" name="Groups" value="[FMP-ValueListItem]" [FMP-ValueListChecked]>[FMP-ValueListItem] [/FMP-ValueList] <!-- After processing, the HTML sent to the browser could look like: <input type="radio" name="Groups" value="Production" >Production <input type="radio" name="Groups" value="Sales" checked>Sales <input type="radio" name="Groups" value="Support" >Support --> Hope this helps.
-
It works (I think) but it won't look great In your search field, try this (I believe this works with the "begin with" operator): ==S*
-
Try this... <select name="related_fp3_filename::related_field"> [FMP-option: related_fp3_filename::related_field, list=value_list_name] </select> Make sure the related field is in your file's -layout specified in your page. You don't have to include the ".fp3" extension for the name of the related fp3 file. [This message has been edited by chandra (edited August 25, 2000).]
-
Since no one else has posted, I'll attempt a suggestion (a.k.a. stab in the dark). If you want to figure out how CDML works with HTML code, I suggest looking at the HTML files for the Employee database that comes with FM Pro 4.1. It should be located in the directory called "employee_database" under the directory "Web". There's semi-decent CDML documentation in the form of HTML comments within the files. If you really love the layout that instant web publishing gives you. I suppose you could save the HTML code and images and insert CDML tags in it, once you are familiar with how they work. Hope this helps!
-
I flipped through my HTML book (HTML, the Definitive Guide, 3rd ed., by Chuck Musciano and Bill Kennedy) and I found the following... quote: With the advent of frames, it is possible to redirect the results of a form to another window or frame. Simply add the target attribute to your <form> tag and provide the name of the window or frame to receive the results. Please post if this works! [This message has been edited by chandra (edited August 18, 2000).]
-
Shameless self-post to bump this thread back to top of the list in hopes of getting a response.
-
First question...I have no idea. I use FM Pro 4.1 and I've never come across an error number -50. Try checking the help file under "Status (CurrentError) function. Second question...In terms of HTML in general and the <form> tag in particular, by default, every element (<input>, <select>, etc.), except hidden ones, is part of a form's tab order. In most cases, the tabbing order of the elements matches the order of the elements within the <form> tag. Theoretically, if you want to control the tab order, there is an attribute for form elements called tabindex which is part of HTML 4.0 standard. I'm not sure if any current browsers support this attribute. On a side note, Internet Explorer has introduced taborder and notab attributes which should work. If you want to try these attributes, you will have to use Custom Web Publishing though. Hope this helps! [This message has been edited by chandra (edited August 16, 2000).]
-
Gee, I feel like one of a very few that is doing this stuff with just a text editor. But hey: CHALLENGES, if they don't kill you, they make you stronger. (But usually they kill you.)