Overcoming Tally ODBC Single-Port Limitation: Multi-Instance Hack Using Tally Gold License

Integration with third-party applications using ODBC is a common requirement for businesses using TallyPrime. However, one of the most frequent technical limitations faced is:

? Tally supports only a single ODBC port per instance

This becomes a challenge when multiple applications need simultaneous access to Tally data.

This article explains a practical workaround (hack) using multi-instance Tally setups, especially applicable when using Tally Gold (Multi-User License).

Understanding the Limitation

? Single ODBC Port Restriction

• Tally allows only one ODBC port per running instance
• Both:
  • ODBC Server Mode
  • ODBC Client Mode
    use the same port

License-Based Constraint

? Tally Silver (Single User)

• Only one Tally instance allowed
• Cannot run multiple instances
• ❌ No workaround possible for multiple ODBC ports

? Tally Gold (Multi-User)

• Supports multiple users / instances
• Runs in server-client architecture
• ✅ Allows workaround using multiple setups

The Multi-Instance ODBC Hack (Working Solution)

? Concept

Install multiple copies of Tally in different folders, each acting as an independent instance with its own ODBC configuration.

Architecture Overview

Application 1 → Tally Instance A → Port 9049  
Application 2 → Tally Instance B → Port 9050

Each application connects to a separate Tally instance, eliminating port conflict.

Step-by-Step Implementation

✅ Step 1: Create Multiple Tally Installations

• Copy Tally folder:

  C:\TallyPrime\

• Paste into:

  C:\TallyPrime_A\
  C:\TallyPrime_B\

• Rename executables if needed:
  • tallyA.exe
  • tallyB.exe

✅ Step 2: Configure Different ODBC Ports

Open each Tally instance:

Instance A:

F1 → Settings → Advanced Configuration → ODBC Port = 9049

Instance B:

F1 → Settings → Advanced Configuration → ODBC Port = 9050

✅ Step 3: Assign Applications

✅ Step 4: Configure Data Access

• Both instances can:
  • Open same company (⚠ caution required)
  • Or separate companies (recommended)

Important Technical Considerations

⚠ Data Integrity Risks

• If both instances:
  • Write data simultaneously → Risk of corruption
• Recommended:
  • One instance = Read-only
  • One instance = Write operations

⚠ Performance Impact

• Running multiple instances:
  • Consumes more RAM/CPU
• Recommended:
  • Use on Server-grade machine

⚠ License Compliance

• Works properly only with:
  • Tally Gold License
• Avoid misuse in Silver version

⚠ Port & Firewall Configuration

• Open ports:
  • 9049
  • 9050
• Ensure:
  • No conflicts
  • Allowed in Windows Firewall

Best Practice Architecture

✔ Recommended Setup

Primary Tally → Data Entry / Write  
Secondary Tally → Reporting / Read-only

Alternative (Better Long-Term Solution)

Instead of hack, consider:

? Middleware Approach

Apps → Middleware → Tally (Single Port)

Benefits:

• No duplication
• No data risk
• Scalable architecture

When to Use This Hack

Use this solution when:

• Multiple applications require simultaneous ODBC access
• Middleware is not feasible
• You are using Tally Gold
• You need quick deployment

When NOT to Use

Avoid this if:

• High transaction volume
• Critical financial environment
• Risk of concurrent writes
• Limited system resources

Troubleshooting

Conclusion

While TallyPrime natively supports only a single ODBC port, businesses using Tally Gold can implement a multi-instance workaround to overcome this limitation.

By installing multiple Tally instances and assigning different ODBC ports, it is possible to enable multiple third-party applications to interact with Tally simultaneously.

However, this approach must be used carefully, with attention to data integrity, system performance, and proper configuration.