IES ConcreteBending User's Guide
Preferences

Most of the preference settings are self-explanatory. A few are documented below. Preference settings are saved on your machine in the IES folder: C:\Users\your.login\AppData\Local\IES\Customer.

Project History Files

We create copies of a project-file when it is saved. These are stored in the C:\Users\your.login\AppData\Local\IES\Customer.\HistoryProjects folder. If you have data corruption or lost a project, you might be able to recover from one of these. The number of days these files are kept is set in the Project section of the preferences. You can turn this feature off (to save disk space or use your own backup mechanisms) by setting the value to zero.

Crash Protection

In addition to history files, for crash protection we will save a copy of your project every few minutes while you are working. The number of minutes used for this auto-save is also shown in the Project section of the preferences. In the event of a program crash the next time ConcreteBending is started a message indicating a recovery project is available and you have the option of opening this saved file. You can turn this feature off by setting the value to zero.

Project, Next Inspector Field on Enter

By default, in the Project Manager, Modify area, when you press the Enter key it sets your input data but does not change focus to the next entry field. The Tab key lets you move from one field to another. You can enable the movement to the next field on the Enter key with this option.

Reports, Customer Logo

You can use your own company logo in text reports (Report Viewer). Ideally you'll use a .bitmap, .jpeg, or .png that is a reasonable shape and size. Most printers print at 300 dpi, so a 2" logo might be 600 pixels square. We will scale your image to fit the header area of the report. You can use a logo anywhere on your machine, but if you drop one in the IES\Customer\ReportLogo.jpg location, we'll find it automatically.

Reports, Maximum Table Rows

Sometimes report tables can be HUGE. This can cause significant performance problems. To avoid this, we will automatically truncate long report tables to avoid long delays. If you have a fast machine or just need to see the entire table, change this number to something large. We've found that 3000 will generate reports in about 30-45 seconds. Set it to ten million to always see the full table. You can sort a truncated table to see any extremes. Generally, changing your report filter settings, say to show a single result-case will shorten up the table.