Using VB for Application

[Peanut2232425]

I am thinking about making an Application in VB on a Sequal Server. Right now the Application is written in BASIC. I want to recreate it in VB & give it a new interface. In BASIC there are about 1900 Alpha-Nurmeric fields, 900 Numeric fields, and 550 Interger fields. There would approx. be about 50-100 users working in the Application.

I am wondering if VB is the best or would be able to handle this work load or if it would experience any dragging on the user end.

I am also wondering what database is the best to use. I doubt if Access would be good enough but, I am not sure. Any advice or comments are greatly appreciated.

 

[MrEGuest]

I am not sure that I understaand you correctly. Are 50-100 users going to be hitting the same exe, like on a network drive? If that is the plan it's not recommended.

The front-end or GUI (the exe)- should sit on each individual client machine. You should then look into creating 2 or 3 ActiveX dlls. One dll to enforce your business rules (i.e. field lengths, required fields, security access, etc.). One dll that contains your data access components to talk to the db. This serves as a bridge between the your business services dll and your actual database. The data access dll can also split into two separate components - one that will contain application specific methods and one that will be generic and can be used by almost any windows client/server database application.

With this type of architecture Visual Basic can definetly handle the specified user-load. Also, at 100 users SQL Server would be able to serve your needs much better that Access.

Hope this helps you get started.
Josh

 

[Peanut2232425]

I was going to put the Application on the network & have an exe file on every user station so, they can get into the Application. I was wondering if VB was ok to use for the Application with that many users.

 

[Guest_imported]

As long as you bridge the database procedure from the buisiness services (as MrEguest so kindly suggested ) VB is more than capable of handleing that work load, and I would definately recomend an SQL based database structure as well.

hope this helps,
Rob