That sux. I have had to handle a few of these (we upgraded to Office 2007) issues as well. I know I can't hold onto yesterday/yesteryear forever, so I am learning to transition. Oh, by the way, that transition includes a lot less M$ related craziness than in the past. For End User client solutions I am always going to be stuck having to deal with these little M$ issues. But for my own internal processing for commercial clients, well, I get to choose the solutions I want to use. And the trend thus far has been to use Ubuntu Linux wherever I can for file servers, Windows XP/2000 Pro only where I must (with VMWare anywhere possible), PostgreSQL is being used to displace the back end data tables wherever as as quickly as I can do so without causing grief (I still LOVE VFP! But PostgreSQL offers better scaling and runs great with Parameterized VFP views)), and my next move is to get my VFP apps to run under WINE/CrossoverOffice - at which point I kiss the internal MS OS goodbye for my commercial production solutions. If I can't get VFP to run correctly under WINE, then I guess I will be making the cut to Python and "little Dabo do ya!"...
At least when using Open Source solutions in a controlled environment (my equipment, my rules), so no M$ stomping on my grapes with their dirty feet... Gil > -----Original Message----- > From: profoxtech-boun...@leafe.com [mailto:profoxtech- > boun...@leafe.com] On Behalf Of Kenneth Kixmoeller > Sent: Tuesday, April 14, 2009 11:29 AM > To: profoxt...@leafe.com > Subject: When will I learn? > > << Warning! Warning!! Microsoft rant ahead! >> > << All who rail about M$ bashing delete this message NOW! >> > << You have been warned. >> > > It happened again. > > Last year, I got a nice little data conversion project which fits one > of my other specialties: publishing with InDesign. So I thunk: what > the heck, just a bunch of text manipulation, why not use the Fox? I > can knock this out fast, Fox will do it well, the client is married > to M$, so no cross-platform issues, etc. > > So I do it. Had a bit of problem with the XML, none of the native > tools seemed to like the files, and hand-parsing it would blow the > budget out of the water. No schema available. So I thought: their Web > firm is pure M$ tools, so I wonder if I can expedite the conversion > with a little two-step? > > I open the XML in Excel, and it converts absolutely flawlessly. Cool. > Quick little automation script, save the converted data as a DBF, and > on with the conversion to InDesign.... > > Worked great. Fast. My InDesign skills saved the client *lots* of > design time. Client was pleased. All was right with the world. > > Fast forward one year -- this is an annual process. (Hear the ominous > music?) The client runs my conversion utility. "It's broken." %^%* > She reports a really weird-sounding error, so I ask her to send me a > screen shot of it. She does so in a Word document, and I see the DOCX > extension. I get this sick feeling in the pit of my stomach. Yes, > they had been persuaded to "upgrade" to Orifice 2007. > > Fast forward: Excel 2007 no longer will create a DBF. > > Now I know I can save it as a CSV and append it into existing > structures. Or maybe I can do something better with the XML bypassing > the automation. Whatever. I can still make it work. But the point is > that M$ changed the rules again. Makes me look like an idiot, and > will cost my client unnecessary $$. > > Ken > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/021d01c9bd19$9f615d00$de2417...@rr.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
