If they don't use classlibs in their Foxpro app, you've got some big hurdles ahead. That they sound open to change, and actually wanting to change are 2 different things thou. It really frustrated me when I still used to attend Foxpro events, or Foxpro forums on the net when Foxpro people would complain all the time how dotnet did something in such a poor way compared to Foxpro. Or that they could do x in one line of code in Foxpro, but they can't figure out how to do it in dotnet. Another reason why I would be hesitant to buy into their being open is I've got a bud working in a VB shop. So they're trying to transition from VB6 to dotnet. And he is frustrated because they all claim they want to do it right, but concepts like encapsulation seem to evade them. There are a couple framework's written for dotnet by ex-Foxpro people. I would assume they selected one of those. I would have hoped that they would have left any of those kind of decisions up to you. They obviously would not have the knowledge to properly evaluate a tool like that. So they've locked themselves in without knowing the why's and wherefore's.

You're correct about the code behind. But it still shouldn't be a major concern. Code's code. Where to put it shouldn't be a major concern. Especially in the beginning. It all get's back to encapsulation. And that encompasses a lot more then just code behind. So I think you have to concetrate there. Codebehind is just a symptom of not doing proper encapsulation. In this case separation of data logic from ui logic. The important question thou, is what level are the Foxpro guys? Are they older, more set in their ways? Do they try to create lots of class libs so their getting a lot of reuse of their code?

I've made the shift from VFP a couple yrs ago. First to Java. Then I moved to another company within the same industry using C#. A couple observations based on my experience: 1) The fact that there is code behind the form is not the biggest, or even a big hurdle to jump over. I didn't have any problems with understanding that a method that I wanted to call is in a separate class or even a separate DLL. 2) Things that are different enough that it will take sometime to get everyone on the same page: a) Inheritance/Polymorphism - It's possible to get some of this functionality in Foxpro, so the difficulty of this one depends on the crew you work with. But things that I've seen some get hung on are Encapsulation, Interfaces. Good class design many get hung up on. But I've examples of those new to dotnet adding methods that manipulate the customer class to the order class, etc. b) Data Handling - There's a big, big difference between data handling in .net and Foxpro. There are people still clinging to VFP because they think that's the only tool that handles data correctly. Good luck on this one. c) Collections - VFP only has arrays. I find that you use collections a whole lot more then I ever used arrays in Foxpro. Something that I found very useful would be a fairly simple app, but enough complexity to give you enough to cover in 3 days. An order form with customer information. And the data stored in a database.

True. But in our case we need something wizbang as we are a startup in an established niche industry. Taking advantage of some of the drawing capabilities that a 3rd party library offers gives us a nice visual impact on startup of the app. Hopefully we will be able to match impact with the rest of the app.

Like I said it was a quick search. Here's a link where WPF is not even mentioned. And it is not easy to do, but I know there is a way since several 3rd party control libraries do support transparent controls: https://dotnetcentral.net/Weblog/posts/247977.aspx[^]

I would think there's a way to get opacity to work at a control level. I use Infragistics controls and I've never had a problem on any controls I've used to get the form background to show thru. I just did a quick google, and this shows one way to do it: http://www.longhorncorner.com/UploadFile/sowba/108252005014532AM/1.aspx?ArticleID=317c80c6-8656-4635-bd7f-39b896768467[^]

This circumstance did not come because of govts requirements to not discriminate. That is a good rule. If a minority meets the same financial criteria I do, and I get a loan but he/she doesn't, that's a problem. The problem arose because of the cheap cost of money due to the very low interest rate. Companies who were greedy set out to make as much money as they could due to the basically free money. So they reduced, if not eliminated requirements for loan approval. This had absolutely nothing to do with the govt forcing them to do anything. Nothing. People without money, regardless of race/color/creed were suddenly able to qualify for morgages. There were certainly some minority neighborhoods decimated because of all the defaults. But at the same time, you have places like Nevada that are having a big problem now because of all the speculators that bought 2nd/3rd, etc. homes there because they could suddenly qualify to get money loaned to them for that purpose.

Gotta say, reading all the messages I've read, all the threads I've seen, this has to be the most racist, ignorant one I've ever read. Did you learn this by attending your weekly KKK meeting? The cause of the problem had absolutely nothing to do with the govt forcing companies to do anything. Other then if you want to say that by the Fed lowering interest rates as far as they did several yrs ago which in turn caused mortgage companies to get extremely greedy, they forced this to occur. From what I understand, many mortgage companies, Countrywide for example, typically bundle up a bunch of their mortgages and sell them to investors. It just so happens that their packages started including many sub-prime mortgages. Which may/may not have been understood by the investors buying these packages. But to say that the cause is the govt forcing companies to sell morgages to minorities is just plain redneck, racist tripe.

I am a big football fan. I used that as an excuse to get Sirius 3 yrs ago. You reaction is similar to mine. After listening to some of their music stations, I wondered how anyone who likes music could listen to FM radio in their car. I live in California, and having satellite radio almost makes getting stuck in traffic acceptable. And the music is not just refreshing cuz it's new. I'm constantly turning on a station and hearing a great song I haven't heard in ages. Not to mention, hearing something I've never heard before, that sounds awesome.

Dang. I'm stuck doing DBF stuff again! But to answer your question, you can use the "CTOD" function as you've seen. Or you can use {} as the field delimiters for an actual date field. So: Insert into Results({09/22/2007})

I believe creating a DBF this way requires that Column names be limited to 10 chars.