Member Avatar for P.manidas

Dear Sir/Madam,

I have a small programe created in VB 6.0 and database MS Access. Where user can insert their only name & address and can retrieve the existing records.

Just for test, I have kept this programe (.exe file and database file) in the share document of a computer and tried to run from another computer. It was running smoothly (I entered records and display that records too). I have not made setup file when i was tested. Just created .exe file.

I want to run this programe in home network that is connected with router. How can i run this programe after installing (I know how to make setup file in VB 6.0) into a computer? Please guide me.

#### There is no server in our Home Network. All computers OS is Windows XP Profesional S2

Edited by P.manidas because: n/a
  • 1 Contributor
  • 2 Replies
  • 287 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by P.manidas

Dani AI

Generated

A reliable, low-risk setup for a small VB6 + Access app on a home LAN is: split the Access database (tables = back-end), put the back-end in a single shared folder on one machine or a NAS, and install the VB6 front-end locally on each workstation. Running the EXE and the MDB directly from a network share can work for quick tests, but it increases the chance of data corruption, poor performance, and file-locking conflicts as soon as more than one user writes at the same time.

Practical checklist

  • Split the database (Access has a Database Splitter or do it manually: move tables to a back-end MDB/ACCDB).
  • Share the back-end folder and set both Share and NTFS permissions so client users can read/write.
  • Prefer UNC paths (\\HostName\Share\MyDB.mdb) in your connection string instead of mapped drives. Mapped letters can differ by user and cause connection failures.
  • Make sure Windows Firewall (or third-party firewalls) allow File and Printer Sharing on the host.
  • Install the VB6 executable and any runtimes locally on each PC; keep the front-end local and point it to the network back-end.

Example DSN-less ADO connection (VB6)

' MDB (Jet 4.0)
Dim cn As ADODB.Connection
Set cn = New ADODB.Connection
cn.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\SERVER\Share\MyDB.mdb;Persist Security Info=False;"
cn.Open

(If you use .accdb files you need the ACE provider: Provider=Microsoft.ACE.OLEDB.12.0; and ensure the ACE engine is installed.)

Troubleshooting & cautions

  • If clients cannot write, verify both share and NTFS permissions and any antivirus real-time scanning that might lock the file.
  • Corruption symptoms often come from running the FE over the network, unstable NICs/cables, or antivirus backups — keep the FE local and compact/repair the BE regularly.
  • Access is fine for a few concurrent users; if you expect heavier use, migrate the back-end to SQL Server Express and use ODBC/ADO for better concurrency and reliability.

Given tested execution from a shared folder, the easiest safety improvement is to split the DB and install the front-end locally while using a UNC path to the shared back-end.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.