I have a database running for a large survey.
The database has 115 fields, although most of them are multiple choice so most end up with only 1 character in them.
However, I too had the same problem when displaying too much data at the one time. Though it wasn't a problem with DBMan, rather the browser.
(namely Netscape)
Netscape has this odd bug, it can't handle a TABLE with 100+ rows.
(my data was originaly all layed out in a single TABLE)
It was a simple fix, breaking up the data into a new table after 50 questions or so.
It might not be the solution here, but it's just a thought.
- Mark
Astro-Boy!!
http://www.zip.com.au/~astroboy/
The database has 115 fields, although most of them are multiple choice so most end up with only 1 character in them.
However, I too had the same problem when displaying too much data at the one time. Though it wasn't a problem with DBMan, rather the browser.
(namely Netscape)
Netscape has this odd bug, it can't handle a TABLE with 100+ rows.
(my data was originaly all layed out in a single TABLE)
It was a simple fix, breaking up the data into a new table after 50 questions or so.
It might not be the solution here, but it's just a thought.
- Mark
Astro-Boy!!
http://www.zip.com.au/~astroboy/
