Comments by pcowie6680

pcowie6680 21-May-10 11:20am View

Thanks Christian. I already toyed with this idea as a way to spread things out to avoid DB size limits and maintain performance, but end up back at the same question - how to turn those multiple databases into something that has the portability, clarity, etc. of a single file.

pcowie6680 21-May-10 11:09am View

I looked at SQLLite when I first started this project some time ago. The documentation clearly recommended against (and still does) using SQLLite on a network filesystem due to locking and performance issues. The lack of stored procedures doesn't matter - all of our DB interaction is through a seperate data access class. I may take a fresh look, given that our use is single-user or very small workgroup and we open and close connections quickly. Still, even if SQLLite solves our problem for now, the challenge of combining multiple files into one is something I'd like to find an answer to. Thanks.

pcowie6680 21-May-10 10:55am View

This is an intriguing possibility. Unfortunately, it is a realm that I have zero experience in (especially how to "put part of the database near the end of the larger file", dealing with file headers, etc.). I'll have to do some learning and experimenting. I'll report back and let you know how it goes, but it will be at least as few days before I can. Thank you.

Comments by pcowie6680 (Top 3 by date)