CodeCharge Studio
search Register Login  

Web Reporting

Visually create Web Reports in PHP, ASP, .NET, Java, Perl and ColdFusion.
CodeCharge.com

YesSoftware Forums -> CodeCharge Studio -> General/Other

 FoxPro.xml

Print topic Send  topic

Author Message
David Wo
Posted: 02/23/2004, 4:54 AM

Does anyone here had created/modified the database component to suit the CCS without need to modify the code just like MS ACCESS? Because I think the date and boolean format are different in Fox DB.
DonB
Posted: 02/23/2004, 2:29 PM

I don't think that will be any problem. You can specify the boolean values
to be whatever the database requires. Look at the Project Properties.

--
DonB

http://www.gotodon.com/ccbth


<DavidWo@forum.codecharge (David Wo)> wrote in message
news:24039f8210259a@news.codecharge.com...
> Does anyone here had created/modified the database component to suit the
CCS without need to modify the code just like MS ACCESS? Because I think the
date and boolean format are different in Fox DB.
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>

Anton
Posted: 03/02/2004, 12:19 AM

Hi David

To be honest, I got fed up of FoxPro / Visual FoxPro after 12 years of using it and always upgrading to the 'best and most stable version'. The ODBC driver has not been updated for some time and has serious security and stability issues. ODBC is a dead path with has fallen off M$ updates.

Visual FoxPro uses something called 'strict date' format which is {^yyyy/MM/dd hh:mm:ss} and boolean format is simply .T./.F. values compared to 0/1 in other databases.

FoxPro 2.6 uses plain dd/mm/yy or dd/mm/yyyy - Y2K problems etc.

If you do use ODBC then, in order to avoid the worst GPFs, you need to issue updates to single rows NOT multiple row updates.

I have a program which automatically up-sizes/translates the referential integrity of a Visual FoxPro database and ports the whole lot (relational rules and table field translations) into MySQL/InnoDB related tables.

Since working with InnoDB tables in MySQL and ditching FoxPro I have 20...25% more of my time to develop real applications.

If you use Visual FoxPro 8.0 OLE DB components then you are bound to a M$ solution which has knock on impact in the choice of web servers you can use. If you use ODBC then you can potentially bring your www server down with GPFs or memory leaks.

Not a nice choice IMO, 'ditch it or be boxed in'...

FoxPro was a nice product in the good old days.

You have more options if your data is Foxpro 2.6 under unix - but that's another story.

Regards

Anton

Add new topic Subscribe to topic   


These are Community Forums for users to exchange information.
If you would like to obtain technical product help please visit http://support.yessoftware.com.

Internet Database

Visually create Web enabled database applications in minutes.
CodeCharge.com

Home   |    Search   |    Members   |    Register   |    Login


Powered by UltraApps Forum created with CodeCharge Studio
Copyright © 2003-2004 by UltraApps.com  and YesSoftware, Inc.