yes you are correct in that part... Access needs no DB server, but MS access is a database right? I have read that its latest version user Object-Oriented DBMS features too. but i am not sure as I don't use it at all!!!
Regards,
-- Abdel Olakara
http://olakara.googlepages.com
Thinking of db is such a waste of time...
U have many portable DB (Java Based embedded) which are smart enough and more importantly open sourced...
Just as an example we JAVA DB(Apache derby) which comes free with JDK 1.6 why not using that..else where going for HSQL...
They are far better when compared to MS-ACCESS which is a proprotiarey solution & have very limited features when used as a RDBMS...Puerly platform independent,Not dependent of Native drivers, Availablity of BLOG,CLOB & RAW datatypes,Triggers... and one of the bigger things is that those can be put under connection pooling by which they could be used more effciently....with support of type IV driver & & finally they can handle 100+ concurrent connection at a time which are surely lacking in MS-ACCESS.
Else where use of XML would be the best thing but still you gonna suffer with either of performance or storage(Main Memory) if you are working on huge dataset.
checouk few links specified below regarding JAVADB
http://weblogs.java.net/blog/forsini/archive/2006/06/java_db_is_now.html
http://developers.sun.com/javadb/
https://glassfish.dev.java.net/javaee5/persistence/persistence-example.html
Hope this might help :)
REGARDS,
RaHuL
we can provide u a clean answer if we know the exact purpose of this applciation ,,,
Generally speaking, if y need data in ur application u HAVE TO use some database , or simply use a file , Excell file , Txt file , property file ....etc
and this is determined by the natural of ur application
Another simple possibility is just to use the java.io.Serializable interface, and serialize your objects to disk, and load/save them as required (on the server of course.
It's still not something I would do through a JSP. The loading/saving should be passed off to a bean somewhere to handle. That way if you decide to implement a database at a later point, you only have to replace that layer of code.
Where databases REALLY come into their own is searching/sorting/reporting through all your data.
> Another simple possibility is just to use the
>java.io.Serializable interface, and serialize your
> objects to disk, and load/save them as required (on
> the server of course.
java serialization is not for Storing Data , it is for Exchanging data and the status of the objetc, so it is not solution