August 31, 2006 at 12:27 pm
I am currently converting our Applications from Paradox to SQL 2005. Majority of our users will be using Express because of cost, and not needing the features in the Workgroup or Standard.
For the most part the process has been easy for one of our applications. This application most of the users have IT staff advaible that have a basic understanding about databases and security.
Now I am beginning to work on the specs for the second application that we are going to convert. One of the issues that we have with this applications is the user base. We have currently 1000 sites on this system every system has their own database on there site. With Paradox there is not a large over head for management of the data, but there is a problem with stablity. It is not the distribution of the database, or the distribution of SQL express that scares me with these users. I know they are going to want to network the database, and with SQL it is more than just mapping a network drive. Is there a easy management tool that I can buy or make so the end user is going to be able to install and run this application over the network. Our users just are not going to understand.
Paul
September 3, 2006 at 2:51 pm
You need to enable the networking part of SQL server during the install then that should be it really unless they are using an existing server.
The rest I tend to build into the application. For example :
When the user first loads the program if there is not database selected or it cant find the correct database it prompts the user to enter the servername or IP address. You can also scan the network for available servers and present the user with a list.
The application will then check if the server contains the correct database and if not ask if the user wants to create (which it does from a script).
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply