Forum Board
-
Hi, I have been trying to look for the source code of a Forum Board that uses MS-Access as the back-end database. Can't seem to find any that uses Access. Hopefully someone can tell me where I can find such a Forum Board. I have found many with MSDE as the back-end database, and do understand the advantages of it, but I am specifically looking for one with Access as the database. Thanks for any help...
-
Hi, I have been trying to look for the source code of a Forum Board that uses MS-Access as the back-end database. Can't seem to find any that uses Access. Hopefully someone can tell me where I can find such a Forum Board. I have found many with MSDE as the back-end database, and do understand the advantages of it, but I am specifically looking for one with Access as the database. Thanks for any help...
I haven't looked for, nor found any forum source that uses Access as a database. However, it seems that you should look for source that uses .NET database access methods (since this is a C# formum). Then, you could modify the database access code to get data from an Access database, which shouldn't require much effort. (You would have to be able to create an Access version of the MSDE database, though.) John
"You said a whole sentence with no words in it, and I understood you!" -- my wife as she cries about slowly becoming a geek. -
Hi, I have been trying to look for the source code of a Forum Board that uses MS-Access as the back-end database. Can't seem to find any that uses Access. Hopefully someone can tell me where I can find such a Forum Board. I have found many with MSDE as the back-end database, and do understand the advantages of it, but I am specifically looking for one with Access as the database. Thanks for any help...
You already asked this and got an answer. If you didn't like it, try http://www.google.com[^]. Besides, Access is a TERRIBLE database to use for a backend for something with many concurrent connections. It's not optimized for it. Either use the MSDE - which is a free but slightly limited (for # of connections) SQL Server complete with ACID capabilities - or use SQL Server. You should use a good RDBMS that runs under a daemon so that the database is always available and handles concurrent connections well, something for which Access (JET databases, to be exact) was never intended.
Microsoft MVP, Visual C# My Articles