database-support

The Startup Manager offers users a variety of troubleshooting tools for interacting with a database that may be damaged.

There are two methods for doing this. Both are pretty simple and straightforward. There is the manual method documented below. There is also an automated method: right-click in chart and choose "Scrub Data". Start with a light scrub and see if that solves the problem. If not, you can either try a heavier scrub or the manual method below. There is a button on the chart toolbar labeled "Edit/Delete Bar/Tick Data" (7th from bottom on right column). It's the black candle with the red X through it.

Windows

Database Restore Points

In Investor/RT Version 11 and after, users can create single or Periodically scheduled Restore Points that can be accessed at a later time in case of an unexpected loss of data or, if a user wants to move the database to another machine . When creating a Restore Point, users can include or exclude Historical data.

Follow these steps periodically to keep Investor/RT running as healthy, lean, fast, and efficient as possible.  Users are recommended to perform a tune-up every 3-4 weeks if not more frequently:

Diagnosing Historical Database Usage

Reason #1 (99% of the cases)  : First, do the obvious thing and check the task bar to make sure Investor/RT is not already running. Investor/RT can not run duplicate instances off the same database at the same time.

Investor/RT for Windows has a built-in warning system designed to alert you if memory usage climbs to abnormal levels.

At some point, you may be asked by our support team to send a copy of your database to us for testing. Use the Restore Point Feature as outlined below:

To create a new Restore Point, go toFile→Functions→Create Restore Point. Be sure to set whether you'd like to include or exclude historical data as shown below. The file will be saved in the archives directory at:

C:\Users\YourUserName\InvestorRT\archives\ where YourUserName is the name you use to log into Windows.