I'm not sure if I should post this here or in the SQL area, because it deals with both SQL and VB.
Right now I have an application which allows users to browse through SQL tables and save portions of the tables to an access database on the network. Recently this access database has been going corrupt at least once a day (and repairing it doesn't always fix it). The database is not too big, we've recreated it many times, so it leads me to believe that the problem is too many users in that database at one time.
What are the problems with writing VB code to allow users to save the portions of the main SQL tables to a SQL table that they can create? I would need to allow them write(create), edit, read, and delete(for a few people).
Do SQL tables/databases corrupt as much as Access Tables/Databases? The users would definately have their own SQL database to store all of these tables.
Any advice/suggestions/links to other posts (though I couldn't find any posts related to this topic) would be greatly appreciated.
ZenEnigma
Right now I have an application which allows users to browse through SQL tables and save portions of the tables to an access database on the network. Recently this access database has been going corrupt at least once a day (and repairing it doesn't always fix it). The database is not too big, we've recreated it many times, so it leads me to believe that the problem is too many users in that database at one time.
What are the problems with writing VB code to allow users to save the portions of the main SQL tables to a SQL table that they can create? I would need to allow them write(create), edit, read, and delete(for a few people).
Do SQL tables/databases corrupt as much as Access Tables/Databases? The users would definately have their own SQL database to store all of these tables.
Any advice/suggestions/links to other posts (though I couldn't find any posts related to this topic) would be greatly appreciated.
ZenEnigma