William E Hatto wrote:A database will handle concurrency (multiple people doing updates to the> Thanks Bob,
> I'll refine the OP a bit more.
> This list (4 in fact, of which some items are moved between) of items
> is shared between 6 people using a mix Mac and PC's. All can view,
> some can add with one user determining the priority. Hence the need
> for a web basewd solution.
> Is it better to use a DB or text file?
data simultaneously) issues better than using a text file, although with
only a couple people being able to maintain data, concurrency may not be a
huge issue. So the deciding factors will be:
1. Is what you are doing now working? Any problems with concurrency? Are
users being prevented from making changes to the data due to other users
making their changes? If not, then, if it ain't broke, don't fix it.
2. Scalability - the text file method will not scale well, so, if you are
faced with the prospect of adding more users, or if the amount of data could
possibly get much greater than what you are now handling, then you do need
to consider moving to a database.
Since we are back to needing to persist the rank order so it will apply to
all users, if you decide use a database, you will need to use the Rank
column I described in my previous reply. Regarding your objection that all
the Rank numbers would need to be re-entered if one row's rank changed, this
is not the case: you do not need to use 1,2,3, ... for the rank numbers. You
can use 100,200,300, ... . If you need to move the 300 row to before the 200
row, simply change its rank to 250. If you are changing the rank a lot, use
1000,2000,3000, ... .
I see that you've posted to .inetserver.asp.db as well, so I've crossposted
this reply there as well as setting Follow-ups for this thread to that
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the