Does anyone know if there is a limit to the number of SYSTEM DSN's you can
have in ODBC manager.

Some of our clients are payroll bureaus and they have a requirement to
create hundreds of databases. In the Btrieve version currently that's not a
problem as we don't make DSN's and the database doesn't appear in PCC. Our
largest client is approaching 1000 database on the same server. (About 16
concurrent users processing them) so access isn't an issue. However, in the
run up to conversion to the relation engine, this issue concerns me.

Any ideas?

Regards
Rowland Costin

I think I remember a bug in an old version that caused it to fail after
400 or so DBNames, but this was fixed a while back. The number of
"supported" DBNames is limited only by the file space of DBNAMES.CFG,
which is typically in the C:\WINDOWS or SYS:SYSTEM directory.

You might have some performance problems logging in with that many
DBNames, simply because of some possible table-scans on the table, but
you'd need to watch it & see...
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - November, 2005 ***
*** Chicago: Pervasive DataExchange Class - November, 2005 ***

Eclipse wrote: