Skip to main content

Rick: FoxPro Rocks Parsing Data

Oh yeah! I had a similar case recently only I had to create a database from about 5 different versions of the same catalog document. The time was a bit different due to manual checking and inconsistent terminology but I could only imagine how much time it would take for a non-VFP developer to do the same.

I wonder how many companies have documents that should really be databases? I'll bet that number is huge.

I know that once all data is saved as XML, it won't make THAT much of a difference, right? (at least that's what we keep getting told - nudge, nudge, wink, wink)

I think when that finally happens, a whole series of new tools wil be needed. I noticed on SednaX, someone was asking for something similar to the BizTalk Document Manager. That tool is very cool but, in my mind, still overly complicated for what some people want or need to do. Maybe there is a need for a lower-end VFP tool to do something similar - in effect, it becomes an automated XSL generator. I know there are some XML tools out there (XML Spy I believe or XML Studio) that do it - anyone have any success with them?

But until all documents are done in XML (which means everyone has to upgrade to a future version of Office or get off the Upgrade Train), there's really only one tool (that I know of) that totally rocks. Any ideas as to what that might be?

Shedding Some Light: FoxPro Rocks Parsing Data

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...