Wecome to the dark side :). Now you understand what some of us have been saying for years. There's nothing you can do in VFP that you can't do in .net somehow. It may not be a single command, it may require some coding, but in the end the result is the same.

Good luck on your journey. Liberty's books are great.



>I've only just begun (could be a song!) to get into VB.NET, but I love it! I'm not sure if it's the .NET or the VB that I'm really liking - hard for me to tell what's what so far - but I should have moved from Foxpro years ago. I'm using Programming Visual Basic 2005 by Jesse Liberty and some of the videos and I'm already sold. Native database be damned; I find it easier to work with Foxpro on the data side, but so far working with the data objects that link to SQL isn't the quagmire that I though that it was going to be. There are lots of nuances in the languages that are close enough for me to feel familiar, and different enough for me to get kinda lost, but overall I'm good. Has anyone done anything that helps Foxpro people understand the VB side of things better than just going cold turkey? That would be kind of cool. I'm knee-deep into the Northwinds stuff and the little things like the interface designer and the ability to automatically create commone code, and that thing that
>changes all the code if you change the name of a variable is sweet. I'm comfortable with Foxpro, but I am a convert. By the way, if anyone knows any place that would hire a going-from-Foxpro-to-VB.NET-developer, let me know; almost to the point of working for leftover coffee grounds. Almost...