Dear Rick,
please has Javascript functions like FileToStr() and SubStr() to split the file content into two 15 Mb HiddenFields on page?
Many thanks again for support

Web Connection 7 supports uploading files larger than 16mb and there's also a sample that uses a JavaScript component to send files in blocks of smaller requests that are put back together on the other end. I believe in v6 there was an example of using plUpload which is another of these libraries that chunk content.

+++ Rick ---

Unfortunately I cannot upgrade from WC 6.05 to WC 7.10 because I would have to change all my projects and it would be a nightmare.
I have many customers and develop exclusively with Web Connection.
In version 7 you added so many changes to leave me out.
I try to undestand plUpload.

I strongly suggest that you "bite the bullet" and convert to WC7. In most cases the changes you must make, are far fewer than you may imagine. And after it's done, you will find that your life is so much easier. At least try it on a copy.

I agree with Tore - you should think again about moving your projects to WC 7, or you'll keep running into more features that you are missing out on. It's true that you will need to make some changes, but I really don't think it would be a "nightmare". As I recall, I got my main project converted in less than a day, and that was well over 50,000 lines of code, some of it dating back to 1998.

--stein

While I generally agree, the problem that Luca faces is that he is using the Web Control Framework that's been discontinued. So moving to 7 unfortunately does require significant changes.

That said, I've done this to several (small/medium) applications and while time consuming it wasn't as bad as I thought it would be. Specifically this message board application and my FoxPro Weblog both originally were created as Web Control Framework sites and I've moved them to Scripts and Templates. I'm glad I made that move in hind sight as it is much easier to manage the code and because both sites rely quite a bit on JavaScript interactions which are easier to manage in the MVC style of development.

It's definitely doable, but it is essentially a UI rewrite. it also helps if the application properly separates business logic from UI logic as both of these did for me so the process mainly involved updating the HTML templates and moving code from the OnLoad() and OnPreRender() handlers into process class methods.

+++ Rick ---

I am sincerely grateful to Rick for being able to give to FoxPro a second life.
If still I work is thanks to WC.
I develop customized software to business customers from 20 years and consider WC a tool as precious as FoxPro.
WC cost is irrelevant compared to its real value.
However, I had problems to upgrade from 5.68 to 6.05 and still I prefer to create new projects into 5.68 version then upgrade them to 6.05
I follow every WC news with much interest, but I cannot upgrade to 7.12 now, I am into production time and every WC problem would affect all projects.
Maybe next holiday time.

Rick, I realize the Web Control Framework is no longer supported, but in my experience there's nothing in those pages that actually breaks under WC 7. My app has at least 20 WCF pages running happily under 7.10.

Frankly, as best I can recall, none of the issues that came up during the transition were specific to those pages. I had to tweak a few things here and there, but most of those pages just worked after moving from WC 6 to 7.

That being said, I would like to start migrating those WCF screens to Template based pages, but management of course would rather see new features that they can show customers as selling points.

--stein

Thanks Stein,

I don't think anything should have broken in v6.5 or 7, but styling is different and some of the support tooling is no longer installed or provided. But yes - nothing was changed with the framework so there's no reason that apps shouldn't be able to run.

Until not too long ago I was running both my FoxPro blog and this message board on WCF pages still so I know it was working. I also can't recall what was involved but like you I started slow by mixing and matching - replacing one page at a time first before eventually getting through all pages of the application 😄 - it's a process.

... but well worth it. As nice as WCF was conceptually with real controls, properties and some persistent state, with modern applications that use script updates in pages in conjunction with server updates it's a huge burden to keep all in your head, plus there was a lot of overhead in all the extra processing to build up the control trees.

It's pretty amazing though that this was actually possible to build with Visual FoxPro, and easily was the most complex part of Web Connection to build and maintain. RIP WCF 😄

+++ Rick ---