Paradox? As opposed to what...Access?

I still do quite a bit of Paradox programming. A new client wants an app that I have written in Paradox. But they want it in Access. So I've started to learn Access. What a piece of crap. (For the record, Paradox 10 and Access XP) Takes much longer to find the correct commands, help is workless, and the reference books are almost useless. Granted, I've used Paradox since DOS version 2, was a development partner, but when I have to hunt trying to save a record (Refresh!? - that should mean refresh the screen, not write a record) or insert a blank record on the screen (DoCmd runCommand cmdRecordGoToNew) and it is not shown in any help... I'd almost prefer to write in COBOL!

But, since I'm a "professional", I'll give the client what they want, in the language they want. And happily deposit their payments. I have told them that it would be cheaper to modify my existing Paradox program (only need to add a couple of fields) than to develop an entirely new application in Access.

C'est la vie!

Post #51,572 by jb4 9/12/02 6:15:44 PM Reply	Paradox? As opposed to what...Access? What kind of a choice is that? jb4 "About the use of language: it is impossible to sharpen a pencil with a blunt axe. It is equally vain to try to do it with ten blunt axes instead. " -- Edsger W.Dijkstra (1930 - 2002) (I wish more managers knew that...)
Post #51,626 by deSitter 9/13/02 10:04:55 AM Reply	Re: Paradox? As opposed to what...Access? Access at the time was light years behind Paradox. Basically MS turned Access (and VB)into what Paradox already was, only without ObjectPAL behind it. But it killed Paradox as a desktop/workgroup database. -drl
Post #51,628 by jbrabeck 9/13/02 10:19:53 AM Reply	Access is even farther behind Paradox I still do quite a bit of Paradox programming. A new client wants an app that I have written in Paradox. But they want it in Access. So I've started to learn Access. What a piece of crap. (For the record, Paradox 10 and Access XP) Takes much longer to find the correct commands, help is workless, and the reference books are almost useless. Granted, I've used Paradox since DOS version 2, was a development partner, but when I have to hunt trying to save a record (Refresh!? - that should mean refresh the screen, not write a record) or insert a blank record on the screen (DoCmd runCommand cmdRecordGoToNew) and it is not shown in any help... I'd almost prefer to write in COBOL! But, since I'm a "professional", I'll give the client what they want, in the language they want. And happily deposit their payments. I have told them that it would be cheaper to modify my existing Paradox program (only need to add a couple of fields) than to develop an entirely new application in Access. C'est la vie! [link\|mailto:jbrabeck@attbi.com\|Joe]
Post #51,635 by drewk 9/13/02 10:42:59 AM Reply	Urrkkkk! DoCmd runCommand cmdRecordGoToNew Talk about taking a good idea to a wildly inappropriate extreme. === Microsoft offers them the one thing most business people will pay any price for - the ability to say "we had no choice - everyone's doing it that way." -- [link\|http://z.iwethey.org/forums/render/content/show?contentid=38978\|Andrew Grygus]

Welcome to IWETHEY!