Mike,
Yeah, that notion actually crossed my mind when I first started this. To be fair, getting the front/back image scanned was a real triumph, and the process with the Canon P-208II which duplex scans, and has an "adjustable" feeder which makes it very easy to feed cards through it is just brilliant. In fact, you can even stack about 10 cards on it and it will do them all at once... now, if I had OCR, I could check to see if their company already existed, if not, add the company, then add them as a contact. I know there are commercial software out there that do this for their "own" systems, and mobiles, as you mention. It's actually where I got the idea to integrate it into our system, mostly because I want an interface (including card scanning) that makes doing the entry easier than not doing the entry.
I'm sure some will criticize me for not buying some package that does this already, and even more foolish for starting modern enterprise system development in VFP 9... the "Dead Language". Well, I happen to have 20+ years prior experience in this dead language (going back to Fox for Dos FoxBase+, and even further back to dBase III and Paradox before it went pear shaped. I just haven't used it so much in the last 10 years. That said, my "learn curve" has been exceedingly short, and I have the framework I put together years ago. In some ways, I'm stronger than I used to be, as it's caused me to look at "old stuff" that I no longer understood, and simplify it.
The business I started only 4 months ago has generated near half a million $USD with a staff of 3. (Not bad for a startup that began with $40.) What we do is pure service, so we have no product overhead, save for a few licensing costs for some of our engineering system software, but we pass hat on to the clients too.
So, what I need is a system that doesn't exist. What we are doing (and I've been working with consultancies for more than 15 years in this field alone), there is no "software" for. There are even few drawing the benefit of knowledge management systems, which would put them a long way down the track. A few try to "kludge" SharePoint into some system, but it's disconnected from too many other things. The IP we are building up as a research company, (one branch of what we do) doesn't exist in any other organization that I've seen (and I've worked for Dell, Uptime Institute, global consultancies...) what we are creating is unique.
So all that said, it may seem crazy to try to replicate some functionality in VFP for our "Enterprise Application" (and by the way, SalesForce, SAP, ERP, CRMs) none of them do what we are doing (though they could be "made to do so", the cost would be significant, we'd have no control over it, and at the end of the day, I've been able to build a large base of our needs in only a few days. Largely thanks as well to the Tek-Tips community, and leveraging "what we know" which in reality is probably what we do best. So for an "internal enterprise IP management system", VFP is fine. I always laugh when I tell people about what I'm building and their first question is "What language are you using"? (99% of these people have never written a line of code in their life, and the ones that have, have never gotten much beyond report writers.) So my reply is always "English".
Though I recently started saying .NET, just because I don't feel like explaining myself. Those who don't program are still surprisingly aware that VFP was canceled by MS in 2007.
The OCR thing is monumental, in the task of parsing even a few small bits of data from front/back of card. You have complexities like some cards (that I have) have 2 addresses on them... Cards in English, Chinese, Spanish, Japanese, Bahasa Indonesia... all going to be a significant challenge, and I expect the "OCR" challenge could even take me a year to tackle, but I will tackle it sooner or later.
For the moment, because there wasn't a reasonable example for me to work from, I've decided to focus on completing some of the other areas. With the front/back card scanning accomplished now, I feel that is more than 1/2 the battle in most cases. And in fairness, it's not really a bad thing for people to enter that data... I'm making getting large amounts of other data into the system exceedingly easy and automated. (450+ data points imported from Excel spreadsheets, which are populated in many cases from exports from the system as well). Templates for "data collection" are established in the database using "code tables" and then thrown at an Excel file write. The users complete the excel sheets, which are tightly controlled for entry, and then it's all sucked back into the system. Decoupling the data collection in this way means we don't need users to have access to our proprietary IP system. And we can give them outputs to Office files (like Word, Excel, PowerPoint) generated from VFP instead of PDFs, as they want to use/edit them, but we can do that by giving them the "raw numbers" but without the IP embedded in the docs. (None of our competitors do this...)
If we become ridiculously successful and a $100million dollar company, then we'll use this as the prototype, and hire someone else to write it, but as a startup... this is awesome. Leveraging the skill set we already have... priceless.
I guess I make this point because I don't want to kludge a mobile phone and mucking with the get data out, get data in... I think it would wind up being more type than just typing a few bits of data off a business card into the system until we can integrate OCR. But I like your out of the box thinking... that's the kind of stuff that leads to real innovation. And I think our bold choice of VFP at this late stage of it's life is actually an innovation in itself.
Best Regards,
Scott
ATS, CDCE, CTIA, CTDC
"Everything should be made as simple as possible, and no simpler."
![[hammer]](/data/assets/smilies/hammer.gif "[hammer] [hammer]")
