Servoy

[Scott24x7]

I know this is the VFP forum, but a friend of mind recently pointed me toward Servoy as a "way to keep my VFP skilset". A quick look at their web site had Ken Levy's name all over it, so I figured there must be some truth to it. I did a quick download of the install, but haven't had a chance to do much with it yet. What is the % similarity to Servoy to VFP, if anyone has made the leap?

Best Regards,
Scott

"Everything should be made as simple as possible, and no simpler."

 

[Olaf Doschke]

Servoy is doing some roadshow in germany, next week they'll demonstrate Servoy in Hamburg. The name is also not new to me, they started advertising with google ads, quite soon after the end of foxpro was announced.

What Servoy has in common with VFP is it's combining GUI, language and a database in one IDE product, so it's similar to foxpro like access is similar to foxpro.

Haven't taken a look inside yet, bt I think both the language and the database are as different to foxpro as access, so there's not much truth in "keeping the skillset". You can't recycle dbfs nor code. Recycling data is quite easy anyway, no matter what other database you use, there's essentially the same structure of tables, fields and field types, referential integrity and SQL.

The servoy language may be more similar to foxpro than VB.Net, VB6 programmers also did not recognize "their" language anymore. .NET is strictly oop, no matter if you choose c# or vb.net, that may be an argument for programmers focused on a procedural approach to use some language that supports this kind of thinking.

Bye, Olaf.

 

[Nifrabar]

fwiw:

http://www.servoy.nl/content.jsp?t=734&mt=393

kr
-Bart

 

[cbasoz]

Last time I checked Servoy (long before) I didn't see a similarity to VFP nor some skillset from VFP that would be to my benefit. It is not for free either. You may as well check MS VS LightSwitch.


Cetin Basoz
MS Foxpro MVP, MCP

 

[Scott24x7]

Cetin,
Thanks, I will have a look at LightSwitch!
-S

Best Regards,
Scott

"Everything should be made as simple as possible, and no simpler."

 

[SBTBILL]

Last I looked access would at least read a dbf.

I'm doing some VB not and have found that I can take some code directly from VFP to VB.

It's mostly the database handling that is totally different. Screens are very similar, change case to select case, IF Thens are about the same.

Biggest difference I see is that in VFP you open a table and work on it. That is the table stays open and connected. In VB and dot.net you grab a snapshot of the data and work on that. The table is normally closed. SQL gets real irritated if you leave a table open.

 

[Olaf Doschke]

If you work with many concurrent users on a DBF based application you can't afford to USE tables in foxpro either. Relations and Filter get sluggish in comparison to SQL Joins and Where.

Even without REFRESH, which messes with the network bandwidth, even as controls and grids rather only read a record or a few of the DBF, this concept only works nice, as long as the database is small and only serves a few users.

Bye, Olaf.