For Existing Users Upgrading To The Latest Version: Our Migration Guide.
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:
This video is made to get you up to speed as quickly as possible with RackForms. We cover all major user interface elements, as also cover how the editor works from the most general level. A must view for all users looking to get up to speed quickly!
Demo jobs showing dozens of features are conveniently located in the editor via this drop down menu:
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.
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.
Although mainly used to showcase features, the videos 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.
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.