home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.databases:7900 comp.os.msdos.programmer:10690
- Newsgroups: comp.databases,comp.os.msdos.programmer
- Path: sparky!uunet!utcsri!torn!utzoo!telly!robohack!ve3ied!bduncan
- From: bduncan@ve3ied.UUCP (Bill Duncan)
- Subject: Re: FoxBase to `C' Contract: How much should I ask for? Help
- Organization: TFMCS
- Date: Mon, 16 Nov 1992 23:23:18 GMT
- Message-ID: <1992Nov16.232318.21234@ve3ied.UUCP>
- References: <1992Nov9.221720.9793@tamsun.tamu.edu> <RcR3TB2w165w@valnet>
- Lines: 38
-
- In article <RcR3TB2w165w@valnet> valnet!herrj@news.cs.indiana.edu writes:
- >tpradeep@cs.tamu.edu (Pradeep K Tapadiya) writes:
- >
- ># Howdy friends,
- >#
- ># I have been approached by a company to write a generic FoxBase to
- ># `C' converter. The user-interface needs to be converted to "printf"
- >
- >Sounds like fun!
- >
- ># So far I used to program on per hour basis. This is the first time
- ># I have been asked to bid for a project. I do not how many man-hours
- ># this work would involve. Since this is my first break, I do not
- ># wish to loose this contract. Would the experienced readers on the
- ># net advice me on how much I should bid for this contract? Any
- ># kind of advise/strategy is appreciated.
- >
- >You might try posting to misc.jobs.contract or looking for its FAQ.
- >Try the latter first.
- >
- >
-
- You don't give us any clue on the scope of the problem. I converted a
- non-trivial FoxBase application (300+ related files) in about a month.
- But it was my own FoxBase code.. ;-), so of course I didn't have the
- ramp up time learning the application.
-
- I developed a number of tools functions which emulated the FoxBase counterparts.
-
- The new system was almost identical in operation, but on avaerage was 16x
- faster, and a fraction of the size (on a MessyDOS machine). The FoxBase
- system required 500+K of RAM which was a problem because of TSR's. The new
- system was done in small model. The executable was about 60K. I forget how
- many LOC there was, but it was non-trivial.
-
- Bill Duncan, (bduncan@ve3ied.uucp)
-
-
-