You will want to use the 2 properties of the .NET#c IDE to de-serIalize the 5 class objects in the Sqlserver 2005 datasets. 3 of these datasets will have 3 more properties running in the RLC running time.
Hope this helps, and best wishers to your Nigerian Uncle and his MOST pressing banking needs.
¡El diablo está en mis pantalones! ¡Mire, mire!
Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!
That everyone uses MySQL seems MySQLs biggest argument.
That was what I meant. We use Postgret here too.
Firebird seems to be an anlternative, but one of the Guys here has extensive PostgresQL experience.
Embedded Firebird turned out to be a good solution to my company's needs. I developped an application that people install on notebooks and use it on remote locations to acquire data and do some calculations and reportings, using Firebird embedded database. Later, those notebooks are connected to their company's network and data is transferred to main SQLServer database for further processing.
"Silence will create respect and dignity; justice and fair play will bring more friends;
benevolence and charity will enhance prestige and position; courtesy will draw benevolence;
service of mankind will secure leadership and good words will overcome powerful enemies"
Ali (Peace be upon him)
Ah yes, but that is not always possible in the case of customers. Some people are content with stuff that works, over total reinstallation of their software, just because the totally uninteresting piece of technology that drives their app, has changed.
Brainwash the customers, provide a new installer with conversion script. This should get them over the SQL more easily.
I had a customer once who insisted on using Access as the backend. This way he could change the data if the application did something wrong. I had a spontanious urge to hit him on the head when I heard his plans.
What about weapons of mass-construction? "What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
I guess many people voted for Access even if they actually meant the Jet Database. I think it makes a huge difference if I'm developing for Access or if I use Jet databases.
As for me, I'm not the one who says Jet is bad in general. If you use it in the right place its a great and straightforward data storage. Sure, Jet is not designed to be accessed by many user at the same time, but so aren't .xml, .doc, .xls and whatever files. So why not using it?
"All languages allow you to write crap code, VB just makes it easier (IMO)." Michael P Butler
I had a vote for Access because we use the Jet database, not the Access front-end, and it was the closest option I could find listed. We use them for local data stores for a distributed application that runs on 100's of user's desktops. However, we are planning on migrating away from Jet and replacing that with SQL Server Compact Edition. It's been a good tool. I have had no problems with using it simply for a data store. We are only moving away from it because Microsoft has dictated that we do.
Couple of reasons you might use Access:
- easy to grab a full backup snapshot from the web host
- some web hosts overcharge for sql server, and you might just need basic DB functionality
- a bit easier to publish your DB; just upload.
- is capable of running moderately busy sites. However if you start getting 2000+ user session per day you might start getting issues with concurrent writes to the Access DB.
But yeah, better to avoid access nowadays esp. if your site will potentially grow to become very busy (SQL 2005 Express is a good an alternative).
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
CP article: SmartPager - a Flickr-style pager control with go-to-page popup layer.