Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Vivek Deodhar
  Where is Vivek Deodhar?
 SANGLI
 India
 Vivek Deodhar
 To: Bernard Bout
  Where is Bernard Bout?
 Brisbane
 Australia
 Bernard Bout
 Tags
Subject: RE: Bernard CA New Tutorial Part 3
Thread ID: 208997 Message ID: 209307 # Views: 5 # Ratings: 0
Version: Visual FoxPro 9 SP2 Category: Databases, Tables and SQL Server
Date: Saturday, December 27, 2008 5:58:12 AM         
   


Hi,

I am experimenting with Mysql 5.1, intending to replace my native VFP tables with mysql.

As a beginner, some queries have cropped up.

1. Should I get a connection handle only once at the start and use it everywhere and then sqldisconnect() at end or should I get a connection handle everytime I want to query something and then immediately disconnect? Which is more efficient way? I am asking this because some samples on net I downloaded had this second method, so I am wondering whether there is some logic behind this frequent connect - disconnect?

2. Currently, I use VFP tables as rowsource in my combo-boxes. Suppose, I have "City" table with a field "CityName". I have a combo box on form to add city to customer records. Currently, If someone else adds a cityname to city table, it is immediately available in the combo box on customer form for all other users. When they drop down combo box, they see this new city in the list.
If I use MySql (or any other such data source), the combo box will have to be filled by means of sql query. How can I make sure that changes made by other users are reflected in the combo box immediately, without a refresh of some sort by user?
(I am giving city only as an example, there are other more important changes that some users might be making which should be reflected to all users immediately. This data has been presented in combo box, grid, list box etc.)

Happy New Year,

vivek

ENTIRE THREAD

Bernard CA New Tutorial Part 3 Posted by Samir Ibrahim @ 12/23/2008 1:18:40 PM
RE: Bernard CA New Tutorial Part 3 Posted by mike castillo @ 12/23/2008 2:14:59 PM
RE: Bernard CA New Tutorial Part 3 Posted by Samir Ibrahim @ 12/23/2008 3:47:39 PM
RE: Bernard CA New Tutorial Part 3 Posted by Bernard Bout @ 12/24/2008 2:23:22 AM
RE: Bernard CA New Tutorial Part 3 Posted by Benny Thomas @ 12/24/2008 7:44:25 PM
RE: Bernard CA New Tutorial Part 3 Posted by Bernard Bout @ 12/25/2008 1:09:05 PM
RE: Bernard CA New Tutorial Part 3 Posted by Benny Thomas @ 12/25/2008 6:57:17 PM
RE: Bernard CA New Tutorial Part 3 Posted by Bernard Bout @ 12/27/2008 6:57:21 AM
RE: Bernard CA New Tutorial Part 3 Posted by vivek deodhar @ 12/27/2008 5:58:12 AM
RE: Bernard CA New Tutorial Part 3 Posted by Bernard Bout @ 12/27/2008 7:04:00 AM
RE: Bernard CA New Tutorial Part 3 Posted by Mike Yearwood @ 12/27/2008 4:06:01 PM
RE: Bernard CA New Tutorial Part 3 Posted by vivek deodhar @ 12/29/2008 5:42:39 AM
RE: Bernard CA New Tutorial Part 3 Posted by Mike Yearwood @ 12/27/2008 4:07:55 PM
RE: Bernard CA New Tutorial Part 3 Posted by Benny Thomas @ 12/28/2008 2:04:35 PM
RE: Bernard CA New Tutorial Part 3 Posted by Bernard Bout @ 12/29/2008 3:41:41 AM
RE: Bernard CA New Tutorial Part 3 Posted by Benny Thomas @ 12/29/2008 9:35:38 AM
RE: Bernard CA New Tutorial Part 3 Posted by Bernard Bout @ 12/29/2008 6:02:04 PM
RE: Bernard CA New Tutorial Part 3 Posted by Mike Yearwood @ 12/29/2008 8:45:10 PM
RE: Bernard CA New Tutorial Part 3 Posted by Bernard Bout @ 12/30/2008 2:50:22 AM
RE: Bernard CA New Tutorial Part 3 Posted by Bernard Bout @ 12/30/2008 2:56:26 AM
RE: Bernard CA New Tutorial Part 3 Posted by Mike Yearwood @ 12/30/2008 4:01:38 AM
RE: Bernard CA New Tutorial Part 3 Posted by Bernard Bout @ 12/31/2008 5:39:06 AM
RE: Bernard CA New Tutorial Part 3 Posted by Mike Yearwood @ 12/31/2008 4:11:38 PM