Claude;

I spent last week at the .NET 2310 course (ASP.NET with VB.NET. I am scheduled for additional classes. We use VB and I will learn C# on my own. I am looking at getting my MSAD to have a good position in the job market. With 127,000 programmers out of work in Silicon Valley, you have to have an edge. Thank God I have a good job at a stable company but you never know about tomorrow. :)

Tom

>You're welcome. I think we can forget about Access and even VB - now it's time to worry about how MS positions VFP against .NET ...
>>Claude;
>>
>>Thank you for the good link. I have actually been to several offices here in the San Francisco Bay Area where a condition of employment for a secretary was use of Access, PageMaker and Word or Word Perfect. The secretary would be in over her head from what the manager expected trying to write complex applications to run the company. Companies can be and are “strange”.
>>
>>Tom
>>
>>
>>
>>>Check out what MS had to say in the comparison of VFP 7 to Access (bottom of article) at: http://www.activevfp.com/dev/qa.asp
>>>>It's been quite a while since I looked at Access and was hoping for some insight as to whether the old VFP is better than Access arguements hold up. i.e. Access more for smaller apps, VFP handles data faster and larger amounts, Access performance drops off as users and/or data size increases, etc.
>>>>
>>>>I have a potential client that has one Access app. Their company (users, money data,etc) has increased by over 5 times. I am suggesting future development be VFP or VFP/SQLServer based, which could access the existing Access data if needed, but they hope to continue with Access because they already have an app in Access.
>>>>
>>>>Confirmation to the above and any other reasons/arguements greatly appreciated.