Settings

The Settings view contains database management, backups, display preferences, image constraints, lot sizes, licensing, legal information and advanced troubleshooting tools.

Navigate to Settings in the sidebar.

Database

The Database section shows the active database path and provides actions such as:

  • New DB - create a new blank database.

  • Open DB - switch to an existing .db file.

  • Import - open the CSV/XLSX importer.

  • Export - export trades to CSV.

  • Backup - create a database backup.

Warning

We recommend creating a backup before using database recovery or replacing the active database.

Demo Mode can import while the journal contains fewer than 20 persisted trades. An authorised import processes the complete selected file and is not truncated at 20. New Database, Restore and other explicitly full-access database replacement actions remain restricted.

Backup Settings

Backup options include reminder settings, startup auto-backup and retained backup count. Keep a separate copy of important database backups outside the application data folder.

Time Format

Choose the preferred 12-hour or 24-hour display format.

Images

Image settings control maximum dimensions, file size and JPEG conversion for screenshots stored inside the local database. Larger image limits increase database size.

Lot Sizes

Lot settings define Units per Lot for a specific account and symbol.

FTJ stores trade quantity in units. The Trades Entry card can display quantity as Units or Lots, but correct Lots conversion requires the correct contract size for the selected account and instrument.

License

The License card shows the current subscription/trial state, provider information, app version and refresh controls.

Paid licensing is handled through Freemius. Microsoft Store is used for installation and updates.

Demo Mode

Without an active subscription or trial, FTJ runs in Demo Mode.

Trade-count behaviour:

  • Manual trade creation is available while fewer than 20 persisted trades exist.

  • CSV/XLSX and broker imports can start while fewer than 20 persisted trades exist.

  • An authorised import is complete and is not truncated at 20 trades.

  • New trades and imports are blocked at 20 or more persisted trades.

  • Existing core trade details remain editable at exactly 20 trades.

  • Above 20 trades, core trade details and execution mutations become read-only.

  • Viewing, Dashboard analytics, export, deletion, journal notes and self-reflections remain available.

  • Deleting to exactly 20 unlocks core editing.

  • Deleting below 20 also re-enables manual creation and imports.

Supporting workflows available in Demo Mode include:

  • creating and managing multiple accounts;

  • managing account cash flows;

  • adding, editing, deleting and fetching exchange rates;

  • broker connection setup, sign-out and link management;

  • limited strategy, confluence and exit-reason creation according to the displayed limits.

The default account, accounts containing trades and exchange rates referenced by trades retain their normal safety protections.

Advanced

Database Recovery

Database Recovery works on a copy and provides validation/repair options intended for troubleshooting. Do not use recovery as a substitute for regular backups.

Debug Logging

Debug logging provides additional broker/import diagnostics. Enable it only while troubleshooting because verbose logs can grow and may affect performance.

Seed Strategies & Exit Reasons

Adds missing built-in strategies, confluences and exit reasons. Existing items are not intentionally duplicated.

Test Tools

The collapsed Test Tools area contains synthetic-data utilities for exploring and evaluating the application.

Large Journal Performance Test is available in both Demo and Full Access. It generates synthetic trades in the active journal so you can evaluate FTJ with a larger trade history.

Available profiles:

  • Core - keeps executions but removes screenshots.

  • Realistic - keeps executions and retains screenshots on about 10% of generated trades.

  • Extreme - keeps executions and retains screenshots on all generated trades.

Demo can run the performance test beyond the normal 20-trade limit. This is a narrow exception for generating performance-test data only. After the test data is added, the normal Demo restrictions still apply to creating new trades and editing core trade details.

Warning

The performance test adds synthetic trades to the current journal, and each run adds another full batch. Use a separate test database when evaluating large tiers or when the active journal contains real trading data so the test data is easy to discard afterward.