Welcome to the RackForms 2 / Express Documentation Site.
Start by selecting a main category below:
- Interface Elements
- Page Elements (The Page Types)
- Form Elements (The Elements You Add To Form Pages)
- Confirmation Elements
- Builder Elements
- Entry Viewer
- User Management
- Help Videos / General Files
- Installation Guides
- Localization
RackForms Learning Resources
We want to make sure you get the most out of RackForms. To help with this goal, we encourage you to check out these great resources:
Demo Jobs
Build 693 And Higher: Demo jobs are now conveniently located from the editor via a drop down menu:
Pre-Build 693: Located in your RackForms folder at:
RackForms/RackForms/goodies/Sample Jobs
You'll find a large selection of jobs that showcase most of the RackForms feature set.
Please note the file at the bottom--this is a short visual guide on how to load and view each demo job.
RackForms User Forums
The forums are often a great place to learn about past problem/solutions, as well as
post your own. You can find the forum at:
rackforms.com/forum
Direct Email Support
Often times the fastest way to find a solution is to email support at support at RackForms dot net. Of course it pays to check the help documentation first, but sometimes you just need a helping hand, and we're always happy to help.
Help Bugs
Sprinkled throughout the RackForms editor
are help bugs: 
These little guys can be very useful for quick hints and tricks for specific places and tasks.
Demo Videos
Although mainly used to showcase features, the video at:
...are often a great place to see the most cutting edge features in action.
Of course we also have traditional help videos, located in the listings at the top of this page.
General Hints
Sometimes it pays to play around bit--to that end, one very useful trick is to create an exact backup of an existing form to use as a test-bed. To make such a duplicate, simply rename your current job to something like: job1-test.
When you click the preview button, your new form is created with the specified name, and the original form is left untouched. You can now play around with the copy of the form, but still have the original to go back to.
Another useful hint is to start small. Often times we'll build a complex form and add a bit of functionality to it that we may not yet fully understand. For example, we build a form that uses the Simple Email module. Later on, we decide that we need to add an SQL+ module to send the forms results to a database. The current form has many fields though, which means the resulting SQL+ logic will be large as well.
In cases like this it's often best to create a brand new jobs that uses a small data set. This way we learn how the SQL+ logic works, but without the fuss of a huge job slowing us down.