| As above. Better integration with MS SQL Server. .net invironment. Somehow permit current users whose work environment is unlikely to move to .NET in the near term to not fall irretrievably behind. Help us leverage our VFP skills as future programming technologies develop. Web integration needs to be built into the system and some simple examples need to be presented. With the better report builder antipated in version 9 ... everything is going to be just perfect. May be the inclusion of some tools to generated HTML component (web form). Strong integration with .Net - More integration with .Net, i.e. handling .Net datasets etc better.
- Get rid of VCX, SCX, (all table formats for code basically) and use a PRG format. This will allow us to utilise it better in our larger team, at the moment it is difficult to get a report on when a line in a method in a VCX was changed for example whereas in our C# code this is simple because of the text based nature of the code. I'd like to be able to build internet apps directly with VFP improve the report generator and web service support More functions for C/S app with better control, more imprevement of CursorAdapter. Would like to use VFP in portable devices conecting to Database Server. I would like to see Visual FoxPro be able to make DLLs that can be xcopied up to a live webserver without having to use IISRESET /STOP. Much like .NET can be copied up. I would like to see VFP market itself as more and more of a compliment to .NET (or even J2EE) based solutions. I realize that it will likely never occur but adding strong typing to VFP would be a major improvement. Concentrate more on modern Web and Mobile technology. Better internet integration with VFP only ... an alternative to .NET .NET I think the major obstacle which makes VFP weak on the market is not related with the features, capabilities or performance, it a common belief that VFP is nonstandard. I beleive full compatibility with .NET will help VFP to gain popularity. Better still would be new versions for Linux and Mac platforms. The tool is wuite optimal for our use. Especially for Germany the marketing of VfP must be improved. The focus of the tool should be published the right way. But I'm in doubt if this will happen because it is not the focus of Microsoft. Glue for different database severs and a tool for knowlegde workers. Lifting the size barriers for most of vfp's items like array elements and string size in europa is the way to go - but the 2GB table/file size barrier must also fall. Vfp basically can handle the same amount of data as in FP2.0 - which was huge in the early nineties but is becoming only "playstuff" nowadays. Better and faster GUI. It must at least keep pace with the .Net world Cleaner IDE and end-user visuals along the lines of VS.NET, possible owner drawing for menu system. Longhorn support?
Keep interopability high on the list of priorities - especially web/xml/soap etc. etc. More generic, with less reliance on OS and DBFs (particularly in the IDE - projects, forms, classes and reports should NOT be stored ina DBF! - at the very least, the saving of metadata to these DBFs should be in a transaction to avoid corruption!
Also should be set up as an individual business unit so it can go in its own direction and not tied to VS and .NET More interaction with TabletPC Built in features to serve data on the web without third party tools. A server component that could work as a local data server on a work station or as a data server on a network server. It would be nice if VFP could serve data to any TCP/IP connection so you could use your desktop app over the Internet. It will slowly die in the same way DOS applications slowly died. DOS applications still exist and are in use today. However, a DOS application is not the preferred development environment. Very few new applications are developed in DOS. For some types of applicaitons a DOS solution can meet the user requirements. VFP is fine... It's Microsoft's positioning with VFP I would like to see improve. They need to actively overcome the negative perception that IT departments have regarding VFP as a serious, enterprise capable development tool. 1. Go above the 2GB file limit.
Up and up :-) I guess more interconnection with the .Net framework. More built-in controls like tree view, slider, progress bar, etc or a brige to .NET WinForms classes or at least update to Microsoft Common Controls 6.0 ActiveX library.
Built-in menu classes.
Support for aplha-blended bitmaps.
VFP.NET !!! Strong Typing, Smoother win32API calls. include it on .Net stuff, This product could become a key development tool if the Microsoft executives ever discovered what they owned: decent marketing is now critical, since long-time, high-profile developers are giving up on FoxPro. Critical errors - such as frequent index corruption - MUST be fixed, and seen to be fixed. For FoxPro to survive in an environment where the manufacturer is ambivilant about it's placement, it must be able to easily work with all other RDMS. Data access is great! But I would like to see more cool controls. Pretty things that the people like. It should go to more of a front end tool. More improvements to the report writer, better integration of sql, better integration into .net. Take just one sp and finaly fix the annoying little flukes that still remain. I would like to see Foxpro become integrated with .net More integration with .NET. I like the strong type concept even if I have to give away backward compatibility.
Developers can't ignore Linux and it would be nice if we can run VFP apps in this OS as well. Beat Oracle Better and easy Integration with Windows API
Better capabilities as a general programming language
Real executable generation
Continue evolving the product while making it more stable. More and more integration with SQL Server (maybe debug stored procs?). Create a VFP to .Net conversion helper program. I think it's great creating better functionality with SQL Server. As MS's choice for small & mid-range businesses. Easier or even native support for SQL. Increased stability (less C00005 errors). Better reporting (I know VFP 9 will include it). Better security. More modern visual controls (like a treeView-grid native control). I'd like to see Microsoft: (1) fix the bugs, (2) improve the report writer, and (3) make object-oriented menus. I'd also like anything that could somehow change people's (negative) attitudes about Visual Foxpro -- at best, it's seen as "not a real programming language", and things are getting worse... Continue improving VFP. If the goal is eventually migrate developers to .NET, then provide some kind of migration kit at the appropriate time. More interopp with .net and stay alive. I would like it to be integrated in .NET with a VFP data access engine accessible through the common language more direction to .NET Become .net development tool, same level as VB, C#, C++ and others I would like to see Visual FoxPro take a more proactive stance in promoting itself as a programming language. Mora integration with WEB, and also to keep growing as is now. I think taht one big place of opportunity for VFP are Schools, if you teach the students VFP, it can have a bigger market in the future Stronger language enforcement, such as expicit variable declaration.
Also I find the compiler to be weak in catching coding errors. Don't be part of .NET, but at the same time, keep evolving to maintain compatibality with newer technologies (upcoming generations of Windows OS, .NET).
MS should allow VFP to run (legally) on any platform that can do so (Linux). The only way that VFP will ever be aggressively sold by MS is if the db engine is stripped from it and vfp developers, just like all others, become defacto sellers of sql-server or msde (even though it's free, msde helps keep MS's name in the minds of users/customers).
MSDE, which is free, covers small business clients. Large clients have the money to spend in SQL Server licenses anyway and they need it because of its added scalability/capabilities.
By having a free, built-in db engine, microsoft is not really doing us any favor. It's helping us dig VFP's grave. Multiplatform. The one thing that concerns me most, about Visual FoxPro, is that versions for platforms other than Windows are neither supported nor planned. This may eventually force me to switch to other programming languages. I would like it to remain separate, but fully able to communicate with other technologies Like many, I think that technically it is already on an excellent path. I would hate to see it crippled by becoming another CLR language. Also, like many, I would like to see Microsoft acknowledge what we are talking about. At the very least, another database comparison spreadsheet from Microsoft that shows features, speed, capacity etc of VFP, SQL*Server, and Access would be very helpful. make it as powerfully and userfriendly
as VB and compatible with .NET & C# Workstation UI please!!! Keep up to date with the latest controls & interfaces. I'd like optional strong typing. Tighter integration with .NET while remaining the flexible tool it has always been. Develop more towards a generic datatool, even if that means letting go of the DBF files we work with now, (Hey, MySQL is cheap as well!) For VFP to have a higher profile among senior IT executives, which would, in theory, make it a viable choice as a development tool.
Better integration with SQL Add a word or two about VFP/Net interop in the .NET advertisements. Remove need for visual component libraries: provide native Treeview control, and better list control (column headers). Better development environment - basic usability of window handling, code editing etc. The only direction left to go is to make VFP natively support the Internet. It takes too many third party tools and time to develop acceptable web applications. web, web, and more web - this could take the form of more interop with .NET I would like much more integrated features to interact with web servers directly from VFP. There exists a few great products to interfact VFP and the web. However, VFP would be much more powerful and much more used as a dev. tool if those kind of products were easily usable natively in VFP. Better intregation with Microsoft SQL Server. UI that matches the current version of Windows. More consistent way to populate controls. Objects, cursors, arrays for all of them. .NET integration LET IT RUN ON LINUX EASILY!! I would like for Microsoft to continue make VFP work well with their SQL Server back end as well as keep up with XP system standards. Continue along the current lines of product evolution with increased visibility as a useful component builder and integrator in dotNET applications. Would like to see scaling for development and deployment of small apps on PocketPC and TabletPC with synchronization features to DBC or SQL Server backend data repositories. More report and printer control.
More Sql enhances Faster access through ADO.
More web oriented tools.
Better integration with other RDBMS (commercial or free).
I think VFP is good to keep on it's track - datacentric programming language. However, it would be good if VFP able to support web development natively. As you can see, most of other programming language like Java, Python, PHP and etc.
Also, I hope VFP can support Window services natively without need ActiveX, overcome versioning problems and attribute programming as .NET I think VFP should work closely with .NET
The reason is simple: .net is (IMHO) currently a big wave on software industry. VFP should be part of it so that it won't drawn to the bottom of the sea!
Have a VFP.NET version (this would probably require giving up some of VFP's features such as macro substitution, but that would be ok). Better support for true database operations. Especially in regard to Triggers and Security We need a better marketing from MS. managing of data is perfect...but we need grafic support to make competitive applications, so, more controls with better grafics and complexity. More Client-Server stuffs, more n-tiers As long as it continues to work with new MS Operating Systems, I'm satisfied. More marketing from MS and books, events, etc, OUTSIDE USA. Integration with .NET
usable with Linux
More connectivities with .NET Very difficult to say. Perhaps the better way is to integrate more and more with the dot net platform, including Yukon. Continue to add features. It is up to the community to raise awareness of VFP in the business world. To a new Owner with some money and not one of the other majors that can't recognize what aint broke! Maybe the best place would be open source.
www.portalfox.com
I have embraced the interoperability of VFP including the Windows API, and will eventually look into .NET for web deployment. I want to see VFP continue on the path of becoming more at home with the other development languages, yet continue to be enhanced as it has. I am very excited about 8 and 9! VFP must stay in the same line, remaing like a standalone product, but full
integrated with the new tecnologies like ADO.NET .NET and RDBMS like SQL Server Integration in .Net Higher profile, more Microsoft corporate evangelizing VFP and for companies to choose VFP for their software application projects. Needs more publicity and marketing in International markets. In Israel for instance, Microsoft Israel never even pronounced the word Foxpro. Make VFP run on top of the CLR NOT A VS language just compile to the CLR Even if no new upgrades features in that version .... So VFP 10.0 only adds CLR compile that would be ok for me... I have looked at VS 2003 and will wait till VS 2005 to test the waters to much work with ADO to get databased programs to work... Don't change. It does exactly what I need it to do. I'd like internal support for Win API structures and I'd also like support built in for callbacks.
I think the Fox is running in the good direction. Maybe (and I'm aware of the problems) it is time to upgrade the 2gb limit. About 10 years ago we could hardly image what 2gb was. In the near future, 2gb is nearly nothing. It should be further tailored and optimized for writing the kind of apps that are not suited to .Net development: quick-turnaround, data-centric, highly data-driven applications, components, and web services. It should continue to get new base controls to enhance the *obviousness* of a version upgrade (from 8.0 to 9.0, for example). For instance, an all-new *super grid* would be a welcome alternative to the 9-year-old VFP grid control, one that drops all the baggage and kludges and makes grids really useful for data entry and display.
VFP is all that's left of what used to be known as the "desktop database" product category. The business needs are not being satisfied by other products, so the potential market is huge. Unfortunately, all vendors (not just M$) are so enamored of the *enterprise* that they don't see how many medium-sized businesses need a high-productivity tool like VFP for line-of-business apps. I'll consider a switch to .Net as soon as it's as good as VFP, or when VFP is finally murdered by Microsoft. From where I stand, .Net appears to be about on Beta 2. I expected much better considering the amount of money Microsoft has poured into it. Newer tools should be clearly better tools, not just ones with a different set of problems and compromises. And it should take less time, not more, to get the same result. On these measures, .NET must be judged a monumental failure - not of the marketplace to recognize the merits of the product - but an abysmal failure of its designers who failed to develop an obviously superior product to its predecessors. VFP .NET [though I know it won't happen] .NET Portability to Linux, further evolution of VFP as a viable, general purpose programming tool. MS should get it out of its closet. This would be a good start. I would like to see VFP rules loosened so that it could be used on linux. Same strategy of marketing used for dotNet with less budget Actually market the darn thing. VFP generates a lot of revenue for MS (VFP developers buy other stuff too)....plus I'm getting tired of everytime I tell someone I use VFP the first thing they say is "wow that's old technology, why you still using that?". It would be nice if MS would make a bigger effort to prevent this. I love the focus as it is now, and would not want to see VFP integrated as a programming language in Dot Net . Just keep going! continue on the same way To support the new Microsoft technology (SQL Server 2005, Longhorn) To create applications for portable equipment. Market as a development language not a database solution .NET Mother of all business and general application languages Much better report writer, better web integration, better ODBC driver, native Linux version. |