The VFP app is using VFP as the backend. We have tons of data and are moving to SQL. His argument is that since we are not using VFP for the backend, why use it at all. We also don't have very many VFP developers here. We have several people that know C#.NET OK, that helps. Next set of questions....
- You say your VFP app is using a VFP database. How were you doing your data access in your VFP app? Remote views, stored procs, pass-thru, etc. Most (not all, but most) people using .NET and SQL Server utilize stored procedures. So you'll need to account for that type of effort. Is your VFP app a desktop app, LAN app, client server app, etc.? (or maybe a better question...is it structured towards a certain architecture?)
- Does your organization/department have any .NET apps running right now?
- Less important, but curious....are your .NET people looking at the beta for VS.NET 2005?
Kevin
