FoxPro Vs. PostgreSQL

[Sai Hertz And Control Systems]

Hello all ,

I am a OpenSource S/W developer and my clients are from remote part of
Himachal Pradesh India.
I am providing my clients,
software
Build on PostgreSQL 7.3.x as backed
and yes , they (clients) ought to save a lot while using my software as
it runs on Linux
But theirs one Prick Our Competitor he is providing solution in what else
FoxPro + Win98
and this competitor justifies his software as Superior because some of
the Indian local banks use this
clumsy set of tool to manage their bureaucratic banking work system.

What I want is some support from this good community to give me some
1. Tips
2. Links
3. Advise
for FoxPro and its limits (As could be told to a layman)
as how to crush my competitor for M$ tools,
Its time to prove The M$ Guys that they have $$$$$ Power and we the GNU
people have a
social perspective of doing work.

Would be greatefull for all your Comments / Bashing and yes Support


Please..........................


To Add More :
My Clients are Agriculture Banks and cannot afford the M$ tools. and yes
all the Win98 installation on their computers are
pirated.

Regards,
V Kashyap

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Jeremy Buchmann]

Post by Sai Hertz And Control Systems
What I want is some support from this good community to give me some
1. Tips
2. Links
3. Advise
for FoxPro and its limits (As could be told to a layman) as how to
crush my competitor for M$ tools,
Its time to prove The M$ Guys that they have $$$$$ Power and we the
GNU people have a
social perspective of doing work.

This may be better posted on a Pg advocacy list, but anyway...

Problems with FoxPro:
1. It corrupts itself frequently. Table indexes, database indexes,
memory files, all tend to get corrupted.
2. Stupid, arbitrary limits on things like string lengths.
3. It's an ancient, dying system that few people know very well.

The first reason will probably be the most important to your customers.
People don't like having to call the computer guy every week or two
when an index gets currupted.

Good luck,
Jeremy


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Matt Johnson]

Foxpro is very solid, especially DOS versions 2.5, and 2.6. It can run for
years without index corruption, which can be fixed with an index on command.
The real glitch is that memo fields are not that reliable.

Post by Jeremy Buchmann

Post by Sai Hertz And Control Systems
What I want is some support from this good community to give me some
1. Tips
2. Links
3. Advise
for FoxPro and its limits (As could be told to a layman) as how to
crush my competitor for M$ tools,
Its time to prove The M$ Guys that they have $$$$$ Power and we the
GNU people have a
social perspective of doing work.

This may be better posted on a Pg advocacy list, but anyway...
1. It corrupts itself frequently. Table indexes, database indexes,
memory files, all tend to get corrupted.
2. Stupid, arbitrary limits on things like string lengths.
3. It's an ancient, dying system that few people know very well.
The first reason will probably be the most important to your customers.
People don't like having to call the computer guy every week or two
when an index gets currupted.
Good luck,
Jeremy
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match