• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 795
  • Last Modified:

ODBC System DSN problem in Visual Basic 6.0


I am creating a software to produce student's transcript in which different department will enter marks for students from their office computers and data should come to a centrally located computer which will have an Access mdb file in a shared folder.

This folder I configured as shared folder across Local Area Network. This shared folder appears as drive letter Z and I create ODBC system DSN on each computer so that my visual basic application running on different computers can access this centralized data using System DSN from Network drive.

It works on each computer 1st time. But PROBLEM COMES when I turn off all computers and restrart next day, visual basic application fails to find ODBC connectivity and I am obliged to go in each computer's ODBC and configure the network drive path again.

If central computer is turn off then it should show the problem but when all computers are turned on then why this problem comes?

How I can make it permanent that each time a client computer wants to access data from centralized access database, it gets without reconfiguration.

Someone advised me to use PHP-MYSQL and make it web-like application but PHP-MYSQL is new for me and I am somehow familiar with Visual Basic 6 and Ms-Access.

How to make Network based database oriented application with proper security and reliability in Visual Basic 6.0 and Ms-Access?

Thanks.

 
0
jatinMCA
Asked:
jatinMCA
1 Solution
 
OP_ZaharinCommented:
"It works on each computer 1st time. But PROBLEM COMES when I turn off all computers and restrart next day, visual basic application fails to find ODBC connectivity and I am obliged to go in each computer's ODBC and configure the network drive path again"

- when you mapped the network drive to Z on every client pc, click on the checkbox 'reconnect at logon' option. this will make sure then the Z drive will always be there after you turn on the computers the next day.
0
 
Robberbaron (robr)Commented:
yes, it would be better to use a real database (MySQL or SQLExpress) as they are true multiuser databases, Both are free and almost as easy to use as access. I use SqlExpress 2008 for all my needs in a 50 user office.

but for your current situation,
it would be better that the DSN refers to a full UNC path if possible.  
instead of Z:\mypath\myaccess.MDB  , try   \\myserver\myshare\mypath\myaccess.MDB . this way it is not limited to user network mappings and may work as a scheduled task where there is no user drive mapping.
0
 
jatinMCAAuthor Commented:
It didn't work in my situation. But I don't see any other answer which i can accept and i want to close the question so that I can ask another question.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now