I suggest you use Microsoft Visual Foxpro ODBC Driver[^]. It has full compatility with other xBase product (including dBase III+), it is newer, and it has much better handling with SQL queries. hth, foxyland

Hi Nalek, a couple of tips from a software developer living in Bandung, West java, Indonesia: 1. DO NOT DRIVE (unless you are immortal. :laugh:) Now, I'm serious. You'll get a nice rental car with an English-speaking driver easily in major cities in Indonesia. Look for "Toyota Rent-a-Car" in yellow pages in your hotel room. If you prefer easy-and-simple, you can contact your travel service (or local travel service upon your arrival) to arrange a city tour. You'll get the tour _with_ the driver _and_ the car in one price :) . Don't depend on cheap public transport. It's horrible. 'Decent' mass public transport only available in the Jakarta. Other than that, if you have to choose, it's better to use taxi (with meter). You'll find "Blue Bird" taxi in most major cities in Indonesia. 2. Most school in Indonesia will be on a long holiday in June and July. So, if you will travel on those months, most sights/tourist places will be crowded especially on weekends (Saturday and Sunday). What style of travel are you interested in? Will you look for an adventure? Or romantic places? Or shopping? Or sight-seeing? Or culinary? I might be able to give you more suggestion if you tell me what you want. (sorry. I know nothing about Sir Lanka. :) ) hth, foxyland

Trekstuff: We might have the same case as you are. You didn't describe what 'the expensive SP' is doing, but in our case it is a cross-tab complex query of about 5 million rows of data. In our case, the time periode is always one month, so we have SQL Agent services that would run the query at 23:00 on each last day of the month. The result then stored in permanent tables on different database. The user would then query their requirement to these tables. The result is satisfying. We just have to 'torture' the server for about 3 to 5 hours on that night. Of course the downside is there are always a specific requirement that the available data warehouse couldn't comply. But we have a policy that they have to request their 'custom' need first to the IT department, and wait for the result for at least one day. That way, we can still have our tea time :) hth, foxyland

Doesn't the backup-database-on-MSSQL2008-and-restore-it-on-azure work? Honestly, I have not use Azure yet, but because it worked on 2000-2005-2008, and I guess, it would work on Azure as well. hth, foxyland

Hi Dan, I don't know what programming language you are using, but here is the logic. I'm sure you can apply it on any language; 1. Create a shared folder with read/write authorization for Everyone on the server. 2. In my apps, every user has their own GUID primary key on the database. 3. Suppose one user has a primary key 0D5FF2C1-9710-47EF-86FE-164E6170EEFD . Each time this user log in to the system, check if there is a text file named 0D5FF2C1-9710-47EF-86FE-164E6170EEFD.TXT in the shared folder on the server. If it doesn't exist, go to step (4). If it exists, try to delete it. If the deletion success, then continue to step (4). If the deletion fail, then other workstation is using this login ID is being used. You might want to show some message and redirect the program flow to the exit routine. 4. Create a text file named 0D5FF2C1-9710-47EF-86FE-164E6170EEFD.TXT on the server and keep it open while the apps is open (don't close the file handle). 5. Upon exit, close the TXT file handle and delete the text file. By locking the handle, as long as the user is login, other client could not delete the file. If the initial client crash somehow, then the lock to the text file would be released by the server OS, thus, other workstation would be able to delete the text file (and login with the user id). Others might have better solution. Yes, this is not a SQL solution. And might not be elegant enough for most programmers/system developer. But it works :) hth, foxyland