DB size limits, how big?

Anon

I'm using an Access db that at present has a little over 5000 records. The members are broken down into subgroups. Some of the subgroups exceeds 400 records. When I query the db by subgroup, I get good result if the subgroup is less than 300 records. When the subgroup approaches 320~340 records and higher, I get:

"The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

A string literal was expected, but no opening quote character was found. Error processing resource 'http://www.sh2fleet.com/wpl/Flotilla.asp?RequestTimeout=5000'. Line 1, Position 144 "

Is there a size limit using XML for Access db queries? No one here can find a way around this.

Page in question is here:
http://www.sh2fleet.com/wpl/FlotMain.htm

[deleted]

"Is there a size limit using XML for Access db queries?"

Access is crap that does not deserve the name 'database' forget about it as quickly as you can, and start using at least MySQL (free), but in an all-windoze environment, consider MS-SQL (expensive).

As for your particular case, it looks like your ASP script fails to generate the XML data, either a timeout or a memory-limit thing. I won't go deeper than that because ASP is basically a piece of crap anyway :-)

tomhath

The ADO Connection and Command objects have CommandTimeout properties that are separate from the RequestTimeout.

[deleted]

With slightly less revolutionary zeal ...

Switch to a proper SQL database. Access was written as a desktop database that an executive can learn how to program over a weekend. It's not meant to be used for anything serious. Indeed, it's such a memory pig that a query can time out with as few records as you've got, which seems to be exactly what's happening.

ASP is also a pig, and while it seems easy because it's familiar VBscript, it will eventually suck all the life, happiness, and well-being out of you as you try to figure out why it's doing weird things. That's in the license agreement... oh wait, ya didn't read it? 😉

Even in a 100% Windoze environment, you can't beat free products like PHP and MySQL. Or PostgreSQL, but I haven't tried that on a windows machine yet. Seriously, give them a try. I just finsihed setting up a query across three tables with over 10,000 records each and a user table with a couple hundred records... works like a charm. Returns the result I need, formatted exactly the way i need it, in under two seconds.

shrug Sorry we can't help you with the problem that you're having, but it's a vendor-created software problem rather than any problem with your code or your data.

Anon

Thanks, fellows. That's what i wanted to hear, some ideas from the non-Windows people. I eventually will move to PHP and MySQL to take advantage of the low costs but for now, with my schedule (yeah, I know, eveyone claims to be so busy 🙂 ) I don't have much time to stop and learn a new system. Access is super simple and that's the kind of tool I need right now.

I came across a Win developer who solved the problem very easily-- in the asp file he added a simple line to extend the server time:

<%@ Language=VBScript %>
<%
Option explicit
Server.ScriptTimeout = 1200 ' 20 minutes
%>

Good grief! I would have thought I could have found that somewhere on the web but this was one what evaded all my searches.

Thanks, guys.
Neal
Subsim.com