Begrænsninger på Access

2Gb Data, otherwise no limit to number of records.
max 255 connnections, although this will in practice be less. Access is NOT a server so it is slower than MS SQL and MySQL.

it-dyret, concrete and measurable answers! Well thats only possible once you have it working. You cant blame Access for bad programming :o)

Your comnment "Jeg har brug for nogle konkrete, målbare svar!" is more than likely the reason why your not getting many answers!

Hi Terry!

It seems one can always count on your in this category! :)

I have posed a similar question i the MySql category http://exp.dk/spm/282258 an got some pretty, good answers - I'm sure you can do the same... :) I'm familiar with programming and have a few years of experience with several languages. Consequently, I know that speed and so forth greatly depends on the programming!

But what if we take on the assumption "All things being equal"? How would you rate Access?? The dude I I'm advising have programmed almost an entire site - which is pretty comprehensive - all by himself, starting out with learning how to programme... Of cause this means that the code isn't top of the notch! What are the limits in accordance to Access?? And how much do you thing he would benefit from shifting to e.g. MySql - what would that do to the db-limitations (without correcting the shortcomings in the code)??

Hi again, just a pluck from your other question, comment form mahler!
(modsat Access, der er velegnet til amatører).

I do NOT agree with comment at all! There are thousands of proffesional sites out there based on Access. 
I agree that other DATABASE SERVERS (MySQL, ORACLE, MS SQL) will be faster and more stable but that does not mean that Access cant be used!

If you expect more than say 20 users reading/writing data at one time, or your data is expected to excede 2Gb  then I would suggest some other. Otherwise I would have nothing against using Access.

When I say 20 users, I mean those reading and writing data from the dB NOT those just viewing pages. Once a page is displayed then it SHOULD NOT use the dB.

Hi again, Terry!

I kind of expected Mahler's comment to provoke you! :)

Thanks for sharing your insight! One final question: what will happen, if the number of users exceed 20 or so?? Will the db become unstable, will it affect performance (speed), will the "extra" users be queued - or what?!?

If you ask Bill he will tell you that Access can actually tell you that you can have 255 connections but in practice it is a lot lower. I dont have much experience with Access on the WEB but I would expect that it wont be possible to make a connection if the limit is reached and I think this limit depends on many factors.
Access is prone to becoming unstable, but this is generally because connections are not closed.
It is VERY important to close connections and use error handling where needed.

I have also heard that dB requests do get buffered by the server but I must admit that I am not sure, and I would never program with that in mind anyway.

Thanks Terry!

I think this last piece of information completed the puzzle... I think my advice will be for the dude to continue using Access until he reaches its limitations and then persuade him to pay me for making him a full-scale pro solution :)

That sounds like a good idea!
and thanks:o)