Vb6 + ms access 2003

[vp75]

We have deployed a VB6 (FRONT END including sql queries in VB6 Coding) with DB as MS Access 2003 project in multiuser operation under windows xp network. For reports we have used crystal report x1

Currently both db and vb6 (executable) is located in network share m/c and all network users has shortcut path of vb6 application. so this is network sharing set up.

My query is do we need to split the MS ACCESS Database (which currently has only tables) and deploy vb6 exe on each client along with front end DB of ms access having all tables link to Back end shared DB after splitting database?



In our project we have some master tables which are rarely updated so can we include this master tables in each user's front end DB ? Will it provide performance gain ? However in sql queries master tables has to refer other transaction tables via joins. Transaction tables has to be reside on back end part of DB.

So can anybody advice for our project is splitting ACCESS DB will help in performance or we should keep it as network share set up

[ItsMe]

I am not sure what you mean by an XP network. Are you using a peer to peer network? Sounds like it is time to upgrade to SQL server and get rid of the Access project file.

[vp75]

It is LAN in which all computers having windows xp professional and in one m/c shared folder we have kept our vb6 exe along with ms access Database. All other M/C has only shortcut path of this vb exe. So my query is splitting db will benifit us i.e. should we put exe + front end database (having link path of back end database after splitting) ? Is it the correct approach in multiuser environment ?

[vp75]

It is LAN in which all computers having windows xp professional and in one m/c shared folder we have kept our vb6 exe along with ms access Database. All other M/C has only shortcut path of this vb exe. So my query is splitting db will benifit us i.e. should we put exe + front end database (having link path of back end database after splitting) ? Is it the correct approach in multiuser environment ? we have suggested client for sql server also but from our end what will be more right approach ? I think putting exe + front end db on client m/c and back end db in shared folder of network will be like client server approach . But will it give any performace boost ?