Supporting CaseWare and Canadian Tax Software Environments

File locking and shared engagement files

CaseWare Working Papers files are frequently shared among multiple staff working on the same engagement, and file locking behaviour determines whether two people can safely work in the file at once or whether one gets locked out unexpectedly. On a file-share deployment, network latency and antivirus scanning can interfere with how locks are acquired and released, producing confusing "file in use" errors even when nobody else has it open.

The fix is the same discipline covered in QuickBooks Desktop multi-user mode troubleshooting: confirm the hosting location, apply narrowly scoped antivirus exclusions, and keep the network path between workstation and file server fast and wired.

Roaming profiles and cloud sync pitfalls

• Staff working from a synced OneDrive folder can end up editing an out-of-date local copy while the server holds a newer version
• Roaming Windows profiles that sync large local caches at logon and logoff can slow down sign-in dramatically during busy periods
• CaseWare Cloud and TaxCycle's cloud features reduce some of this risk but require reliable internet and correctly configured accounts
• Multiple staff opening the same file from different sync clients (OneDrive on one machine, a mapped drive on another) is a common cause of version conflicts

Keeping workstations fast enough for engagement files

CaseWare and tax-preparation files grow substantially over the life of a corporate engagement, and older or underpowered workstations struggle to open and calculate large files quickly. Sufficient RAM, a solid-state drive, and up-to-date software versions matter more for these applications than for general office use, because tax calculations and CaseWare's linking engine are genuinely resource-intensive.

Standard checks during a slow-performance ticket

1. Confirm the file is being opened from its intended location, not a stale local or synced copy
2. Check for outdated software versions; CaseWare, Profile, and TaxCycle all release performance fixes regularly
3. Verify workstation specifications meet or exceed the vendor's recommended requirements for the current file size
4. Review antivirus exclusion scope for the relevant application folders
5. Test network latency and stability between the workstation and any shared file location

Where vendor support boundaries sit

CaseWare, Wolters Kluwer (Profile), and TaxCycle each own their application's calculation accuracy, feature functionality, licensing, and software defects. They do not manage the firm's network, workstations, antivirus configuration, or file-server setup, which is where most day-to-day performance and access problems actually originate. A well-run accounting IT environment resolves the infrastructure side quickly and only escalates to the vendor when the issue is genuinely inside the application itself.

Connecting this to the rest of the firm's IT

These same file-share and network principles apply across a firm's accounting stack, including QuickBooks and Sage 50, and become especially important heading into peak filing periods, covered in preparing your accounting firm's IT for tax season.

Frequently asked questions