Re: SWFox 2019 recap
Yes, and from report back from Tore Bleken, who attended the post-conference X# training, 33 attendees (36 started, but had to leave early), which is 50% of registrations (67). Makes for quite a buzz in the way forward for VFP developers. The DevTeam also listens and I am sure what was discussed at the session will somehow find its way into the VFP language syntax support in X#. The X# user base is definitely looking forward to accept our "long lost" cousins into the world of XBase.NET!!! On 2019/10/30 20:53, Matt Slay wrote: Another interesting thing to follow at SWFox 2019 was the X#.Net open source language, and how they are making good progress with supporting the FoxPro language in X#.Net Eric Selje presented a session on it, and two people from the X# Developer Team flew over (from the Netherlands, and France) to have a vendor booth and sessions. I recorded a video of the X# Dev Team presentation (from my iPhone) and posted it on YouTube here: https://youtu.be/wA61SryiMlk X# web site has download link to the code presented at the SWFox vendor session: https://www.xsharp.info/articles/presentations-and-examples-from-sw-fox - Matt Slay On 10/30/2019 1:38 PM, Eric Selje wrote: Great recap of VFP Advanced, Richard. And yes you did great Tracy! Great to see you there, and would love to see more next year. Eric On Wed, Oct 30, 2019 at 10:43 AM Richard Kaye wrote: And further to that, a big, big shout-out to Doug, Rick & Tamar, and all the speakers for making this happen. The amount of work that goes into pulling off something like this is a labor of love, and Geek Gatherings deserves all the love they get in return. Here are a few of my highlights: In a session on internationalization, Cathy Poutney announced that Steven Black's INTL Toolkit is now open source. If you need a framework that handles translations for different languages or even industries, head over to Github and download it. The aforementioned Cathy Poutney did a session on, what else, extending the reporting engine with a framework she's calling fxReports. This is (or will be soon) available as an open source project in VFPx. Eric Selje did a very interesting session called "VFP Advanced: Is this the next version of Visual Foxpro?". Basically a rocket scientist lone developer in China has reverse engineered VFP, and patched at least 96 bugs (to date) in our favorite tool and its runtimes. All you need to try this out is a licensed copy of VFP9 SP2, hotfix3, and you can install this side by side. He has also released a 64 bit version. There are pros and cons to using the 64 git version. For example, he has not breached the 2GB file size limitation. OTOH it uses newer supported versions of the C++runtime (10.1, I believe) instead of the apparently out of support 7.1 library that VFP is written in. -- rk -Original Message- From: ProfoxTech On Behalf Of Richard Kaye Sent: Wednesday, October 30, 2019 12:44 PM To: profoxt...@leafe.com Subject: RE: SWFox 2019 recap I was not a presenter, like Tracy , but I also had a great time at SWFox. It's a joy to spend time with one's peers learning new (and sometimes old) things, as well as meeting in person with both old and new friends. I would also encourage anyone on this list who still works with the Fox to consider attending next year's conference, which is scheduled for November 12-15, 2020. -- rk -Original Message- From: ProfoxTech On Behalf Of Tracy Pearson Sent: Wednesday, October 30, 2019 12:38 PM To: profoxt...@leafe.com Subject: SWFox 2019 recap I am back to calm after the first day back to work. I had a great time at the conference and hope to stay connected with those I met. I answered an email this morning and thought about the conversation I had with Richard Kaye. Good conversations, good information, and a fun time. I hear I did well as my first time speaking at the conference. Maybe we can get more ProFoxers to go in 2020. See you around! Tracy [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/748bd835-8b11-a4a7-fd62-5651bf51a...@xsinet.co.za ** 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.
Re: lists
https://mail.leafe.com/mailman/listinfo/profoxOT-free On Wed, Oct 30, 2019 at 3:00 PM Matt Slay wrote: > > [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/cacw6n4ty8n9gbdusl2_tzc8pgaqntop+oy6d+vjktue1eox...@mail.gmail.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.
RE: SWFox 2019 recap
I liked that Doug brought up the Windows 10 Pro/Enterprise has a built in Windows Sandbox. If you don't have a VM, this is an instant VM. It allows you to do install testing quickly on a clean machine. I checked. Windows 10 Home does not have the ability to add the feature. Here's a link explaining how to install it, and what it is doing. https://techcommunity.microsoft.com/t5/Windows-Kernel-Internals/Windows-Sand box/ba-p/301849 Tracy -Original Message- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Richard Kaye Sent: Wednesday, October 30, 2019 3:09 PM To: profoxt...@leafe.com Subject: RE: SWFox 2019 recap Thanks, Eric. It was great to meet you in person. I think we have to get some ProFox t-shirts for next year so we can fly the list's true colors... One other thing I wanted to mention. Rick Schummer has built a replacement for the menu designer and will be releasing that as open source as well. The native menu designer is one of the oldest things in the product and Rick's replacement will make managing MNX based menus so much more efficient. -- rk -Original Message- From: ProfoxTech On Behalf Of Eric Selje Sent: Wednesday, October 30, 2019 2:38 PM To: profoxt...@leafe.com Subject: Re: SWFox 2019 recap Great recap of VFP Advanced, Richard. And yes you did great Tracy! Great to see you there, and would love to see more next year. Eric On Wed, Oct 30, 2019 at 10:43 AM Richard Kaye wrote: > And further to that, a big, big shout-out to Doug, Rick & Tamar, and > all the speakers for making this happen. The amount of work that goes > into pulling off something like this is a labor of love, and Geek > Gatherings deserves all the love they get in return. > > Here are a few of my highlights: > > In a session on internationalization, Cathy Poutney announced that > Steven Black's INTL Toolkit is now open source. If you need a > framework that handles translations for different languages or even > industries, head over to Github and download it. > > The aforementioned Cathy Poutney did a session on, what else, > extending the reporting engine with a framework she's calling > fxReports. This is (or will be soon) available as an open source project in VFPx. > > Eric Selje did a very interesting session called "VFP Advanced: Is > this the next version of Visual Foxpro?". Basically a rocket scientist > lone developer in China has reverse engineered VFP, and patched at > least 96 bugs (to date) in our favorite tool and its runtimes. All you > need to try this out is a licensed copy of VFP9 SP2, hotfix3, and you > can install this side by side. He has also released a 64 bit version. > There are pros and cons to using the 64 git version. For example, he > has not breached the 2GB file size limitation. OTOH it uses newer > supported versions of the C++runtime (10.1, I believe) instead of the > apparently out of support 7.1 library that VFP is written in. > > -- > > rk > > -Original Message- > From: ProfoxTech On Behalf Of Richard > Kaye > Sent: Wednesday, October 30, 2019 12:44 PM > To: profoxt...@leafe.com > Subject: RE: SWFox 2019 recap > > I was not a presenter, like Tracy , but I also had a great time > at SWFox. It's a joy to spend time with one's peers learning new (and > sometimes old) things, as well as meeting in person with both old and > new friends. I would also encourage anyone on this list who still > works with the Fox to consider attending next year's conference, which > is scheduled for November 12-15, 2020. > > -- > > rk > > -Original Message- > From: ProfoxTech On Behalf Of Tracy > Pearson > Sent: Wednesday, October 30, 2019 12:38 PM > To: profoxt...@leafe.com > Subject: SWFox 2019 recap > > I am back to calm after the first day back to work. > I had a great time at the conference and hope to stay connected with > those I met. > I answered an email this morning and thought about the conversation I > had with Richard Kaye. > > Good conversations, good information, and a fun time. > > I hear I did well as my first time speaking at the conference. > > Maybe we can get more ProFoxers to go in 2020. > > See you around! > Tracy > [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/001201d58f57$485849d0$d908dd70$@powerchurch.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.
RE: SWFox 2019 recap
The comments on SWFox make me wish I was 20 years younger and still working professionally with the Fox - oh, and could afford to get to visit the meeting John John Weller 01380 723235 07976 393631 ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/041701d58f57$29e13750$7da3a5f0$@johnweller.co.uk ** 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.
RE: SWFox 2019 recap
Thanks, Eric. It was great to meet you in person. I think we have to get some ProFox t-shirts for next year so we can fly the list's true colors... One other thing I wanted to mention. Rick Schummer has built a replacement for the menu designer and will be releasing that as open source as well. The native menu designer is one of the oldest things in the product and Rick's replacement will make managing MNX based menus so much more efficient. -- rk -Original Message- From: ProfoxTech On Behalf Of Eric Selje Sent: Wednesday, October 30, 2019 2:38 PM To: profoxt...@leafe.com Subject: Re: SWFox 2019 recap Great recap of VFP Advanced, Richard. And yes you did great Tracy! Great to see you there, and would love to see more next year. Eric On Wed, Oct 30, 2019 at 10:43 AM Richard Kaye wrote: > And further to that, a big, big shout-out to Doug, Rick & Tamar, and > all the speakers for making this happen. The amount of work that goes > into pulling off something like this is a labor of love, and Geek > Gatherings deserves all the love they get in return. > > Here are a few of my highlights: > > In a session on internationalization, Cathy Poutney announced that > Steven Black's INTL Toolkit is now open source. If you need a > framework that handles translations for different languages or even > industries, head over to Github and download it. > > The aforementioned Cathy Poutney did a session on, what else, > extending the reporting engine with a framework she's calling > fxReports. This is (or will be soon) available as an open source project in > VFPx. > > Eric Selje did a very interesting session called "VFP Advanced: Is > this the next version of Visual Foxpro?". Basically a rocket scientist > lone developer in China has reverse engineered VFP, and patched at > least 96 bugs (to date) in our favorite tool and its runtimes. All you > need to try this out is a licensed copy of VFP9 SP2, hotfix3, and you > can install this side by side. He has also released a 64 bit version. > There are pros and cons to using the 64 git version. For example, he > has not breached the 2GB file size limitation. OTOH it uses newer > supported versions of the C++runtime (10.1, I believe) instead of the > apparently out of support 7.1 library that VFP is written in. > > -- > > rk > > -Original Message- > From: ProfoxTech On Behalf Of Richard > Kaye > Sent: Wednesday, October 30, 2019 12:44 PM > To: profoxt...@leafe.com > Subject: RE: SWFox 2019 recap > > I was not a presenter, like Tracy , but I also had a great time > at SWFox. It's a joy to spend time with one's peers learning new (and > sometimes old) things, as well as meeting in person with both old and > new friends. I would also encourage anyone on this list who still > works with the Fox to consider attending next year's conference, which > is scheduled for November 12-15, 2020. > > -- > > rk > > -Original Message- > From: ProfoxTech On Behalf Of Tracy > Pearson > Sent: Wednesday, October 30, 2019 12:38 PM > To: profoxt...@leafe.com > Subject: SWFox 2019 recap > > I am back to calm after the first day back to work. > I had a great time at the conference and hope to stay connected with > those I met. > I answered an email this morning and thought about the conversation I > had with Richard Kaye. > > Good conversations, good information, and a fun time. > > I hear I did well as my first time speaking at the conference. > > Maybe we can get more ProFoxers to go in 2020. > > See you around! > Tracy > [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/dm6pr10mb340124c0e505f6b6e5d4ac9ed2...@dm6pr10mb3401.namprd10.prod.outlook.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.
lists
___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/cc3990dc-a7e9-425b-80e9-9ac822d59...@jordanmachine.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.
Re: SWFox 2019 recap
Another interesting thing to follow at SWFox 2019 was the X#.Net open source language, and how they are making good progress with supporting the FoxPro language in X#.Net Eric Selje presented a session on it, and two people from the X# Developer Team flew over (from the Netherlands, and France) to have a vendor booth and sessions. I recorded a video of the X# Dev Team presentation (from my iPhone) and posted it on YouTube here: https://youtu.be/wA61SryiMlk X# web site has download link to the code presented at the SWFox vendor session: https://www.xsharp.info/articles/presentations-and-examples-from-sw-fox - Matt Slay On 10/30/2019 1:38 PM, Eric Selje wrote: Great recap of VFP Advanced, Richard. And yes you did great Tracy! Great to see you there, and would love to see more next year. Eric On Wed, Oct 30, 2019 at 10:43 AM Richard Kaye wrote: And further to that, a big, big shout-out to Doug, Rick & Tamar, and all the speakers for making this happen. The amount of work that goes into pulling off something like this is a labor of love, and Geek Gatherings deserves all the love they get in return. Here are a few of my highlights: In a session on internationalization, Cathy Poutney announced that Steven Black's INTL Toolkit is now open source. If you need a framework that handles translations for different languages or even industries, head over to Github and download it. The aforementioned Cathy Poutney did a session on, what else, extending the reporting engine with a framework she's calling fxReports. This is (or will be soon) available as an open source project in VFPx. Eric Selje did a very interesting session called "VFP Advanced: Is this the next version of Visual Foxpro?". Basically a rocket scientist lone developer in China has reverse engineered VFP, and patched at least 96 bugs (to date) in our favorite tool and its runtimes. All you need to try this out is a licensed copy of VFP9 SP2, hotfix3, and you can install this side by side. He has also released a 64 bit version. There are pros and cons to using the 64 git version. For example, he has not breached the 2GB file size limitation. OTOH it uses newer supported versions of the C++runtime (10.1, I believe) instead of the apparently out of support 7.1 library that VFP is written in. -- rk -Original Message- From: ProfoxTech On Behalf Of Richard Kaye Sent: Wednesday, October 30, 2019 12:44 PM To: profoxt...@leafe.com Subject: RE: SWFox 2019 recap I was not a presenter, like Tracy , but I also had a great time at SWFox. It's a joy to spend time with one's peers learning new (and sometimes old) things, as well as meeting in person with both old and new friends. I would also encourage anyone on this list who still works with the Fox to consider attending next year's conference, which is scheduled for November 12-15, 2020. -- rk -Original Message- From: ProfoxTech On Behalf Of Tracy Pearson Sent: Wednesday, October 30, 2019 12:38 PM To: profoxt...@leafe.com Subject: SWFox 2019 recap I am back to calm after the first day back to work. I had a great time at the conference and hope to stay connected with those I met. I answered an email this morning and thought about the conversation I had with Richard Kaye. Good conversations, good information, and a fun time. I hear I did well as my first time speaking at the conference. Maybe we can get more ProFoxers to go in 2020. See you around! Tracy [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/3c00939c-4b61-7668-341a-372ae7a2a...@jordanmachine.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.
Re: SWFox 2019 recap
Great recap of VFP Advanced, Richard. And yes you did great Tracy! Great to see you there, and would love to see more next year. Eric On Wed, Oct 30, 2019 at 10:43 AM Richard Kaye wrote: > And further to that, a big, big shout-out to Doug, Rick & Tamar, and all > the speakers for making this happen. The amount of work that goes into > pulling off something like this is a labor of love, and Geek Gatherings > deserves all the love they get in return. > > Here are a few of my highlights: > > In a session on internationalization, Cathy Poutney announced that Steven > Black's INTL Toolkit is now open source. If you need a framework that > handles translations for different languages or even industries, head over > to Github and download it. > > The aforementioned Cathy Poutney did a session on, what else, extending > the reporting engine with a framework she's calling fxReports. This is (or > will be soon) available as an open source project in VFPx. > > Eric Selje did a very interesting session called "VFP Advanced: Is this > the next version of Visual Foxpro?". Basically a rocket scientist lone > developer in China has reverse engineered VFP, and patched at least 96 bugs > (to date) in our favorite tool and its runtimes. All you need to try this > out is a licensed copy of VFP9 SP2, hotfix3, and you can install this side > by side. He has also released a 64 bit version. There are pros and cons to > using the 64 git version. For example, he has not breached the 2GB file > size limitation. OTOH it uses newer supported versions of the C++runtime > (10.1, I believe) instead of the apparently out of support 7.1 library that > VFP is written in. > > -- > > rk > > -Original Message- > From: ProfoxTech On Behalf Of Richard Kaye > Sent: Wednesday, October 30, 2019 12:44 PM > To: profoxt...@leafe.com > Subject: RE: SWFox 2019 recap > > I was not a presenter, like Tracy , but I also had a great time at > SWFox. It's a joy to spend time with one's peers learning new (and > sometimes old) things, as well as meeting in person with both old and new > friends. I would also encourage anyone on this list who still works with > the Fox to consider attending next year's conference, which is scheduled > for November 12-15, 2020. > > -- > > rk > > -Original Message- > From: ProfoxTech On Behalf Of Tracy Pearson > Sent: Wednesday, October 30, 2019 12:38 PM > To: profoxt...@leafe.com > Subject: SWFox 2019 recap > > I am back to calm after the first day back to work. > I had a great time at the conference and hope to stay connected with those > I met. > I answered an email this morning and thought about the conversation I had > with Richard Kaye. > > Good conversations, good information, and a fun time. > > I hear I did well as my first time speaking at the conference. > > Maybe we can get more ProFoxers to go in 2020. > > See you around! > Tracy > [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/CAAwxvUm1KGd_6m4K=1azm5zb_ku0u5zxyf20kjjj1nmbgst...@mail.gmail.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.
Re: Exporting Tables
True. Yeah - LLIO can be more convoluted to code - I'm just more used to doing it that way that the TEXT command, thus why I suggested it. Will surely have to seriously consider the TEXT command more so in the future. -K- On 10/30/2019 9:46 AM, Richard Kaye wrote: You don't need LLIO. TEXT...ENDTEXT will do the trick just fine as well as allow you to pre-process any of the data like swapping out CRLF with spaces. -- rk -Original Message- From: ProfoxTech On Behalf Of Kurt at VR-FX Sent: Wednesday, October 30, 2019 12:43 PM To: profoxt...@leafe.com Subject: Re: Exporting Tables Hey RK - I was thinking the same thing. Essentially - Gene - you could do the direct export of data - but, to a CSV file. Then, use lo-level file handling to add the memo field onto each line, and, as RK said - make sure to add in the CRLF. -K- On 10/30/2019 7:42 AM, Richard Kaye wrote: I believe this goes back to dBase compatibility and these commands do the same thing. It's not too hard to roll your own CSV/Tab delimited file in which case you can keep your memo fields mostly intact. You will need to convert embedded CRLF in order to keep one record per line. -- rk -Original Message- From: ProfoxTech On Behalf Of Tracy Pearson Sent: Wednesday, October 30, 2019 10:08 AM To: profoxt...@leafe.com Subject: RE: Exporting Tables Gene, I have not seen a difference in the output of the two commands. You might want to consider looking at Craig Boyd's post about exporting and importing from Excel. It doesn't mention Memo fields that I could see. https://www.sweetpotatosoftware.com/blog/index.php/2008/09/30/using-ex cel-20 07-file-formats-in-vfp-9-0/ HTH, Tracy -Original Message- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Gene Wirchenko Sent: Wednesday, October 30, 2019 9:58 AM To: profoxt...@leafe.com Subject: Exporting Tables Hello: I am having to do a bunch of data export so have had a closer look at the commands. 1) I am wondering if there is a difference between COPY TO ... TYPE ... and EXPORT TO ... TYPE ... where the type is XLS or XL5. 2) I know that memo columns are not exported so for tables with them, I am creating a cursor with the memo columns replaced with C(254) columns. In a few cases, this will result in data being clipped. Short of programming my exports to use Office Automation, is there a way around this? (I mean that is not a kludge. For example, I could create multiple columns each with a piece of the memo, but that would be horribly ugly.) Sincerely, Gene Wirchenko [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/22d02c2e-76fc-1991-9737-1432e7c07...@optonline.net ** 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.
RE: SWFox 2019 recap
And further to that, a big, big shout-out to Doug, Rick & Tamar, and all the speakers for making this happen. The amount of work that goes into pulling off something like this is a labor of love, and Geek Gatherings deserves all the love they get in return. Here are a few of my highlights: In a session on internationalization, Cathy Poutney announced that Steven Black's INTL Toolkit is now open source. If you need a framework that handles translations for different languages or even industries, head over to Github and download it. The aforementioned Cathy Poutney did a session on, what else, extending the reporting engine with a framework she's calling fxReports. This is (or will be soon) available as an open source project in VFPx. Eric Selje did a very interesting session called "VFP Advanced: Is this the next version of Visual Foxpro?". Basically a rocket scientist lone developer in China has reverse engineered VFP, and patched at least 96 bugs (to date) in our favorite tool and its runtimes. All you need to try this out is a licensed copy of VFP9 SP2, hotfix3, and you can install this side by side. He has also released a 64 bit version. There are pros and cons to using the 64 git version. For example, he has not breached the 2GB file size limitation. OTOH it uses newer supported versions of the C++runtime (10.1, I believe) instead of the apparently out of support 7.1 library that VFP is written in. -- rk -Original Message- From: ProfoxTech On Behalf Of Richard Kaye Sent: Wednesday, October 30, 2019 12:44 PM To: profoxt...@leafe.com Subject: RE: SWFox 2019 recap I was not a presenter, like Tracy , but I also had a great time at SWFox. It's a joy to spend time with one's peers learning new (and sometimes old) things, as well as meeting in person with both old and new friends. I would also encourage anyone on this list who still works with the Fox to consider attending next year's conference, which is scheduled for November 12-15, 2020. -- rk -Original Message- From: ProfoxTech On Behalf Of Tracy Pearson Sent: Wednesday, October 30, 2019 12:38 PM To: profoxt...@leafe.com Subject: SWFox 2019 recap I am back to calm after the first day back to work. I had a great time at the conference and hope to stay connected with those I met. I answered an email this morning and thought about the conversation I had with Richard Kaye. Good conversations, good information, and a fun time. I hear I did well as my first time speaking at the conference. Maybe we can get more ProFoxers to go in 2020. See you around! Tracy [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/dm6pr10mb340181f899e36aba64090413d2...@dm6pr10mb3401.namprd10.prod.outlook.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.
RE: Exporting Tables
You don't need LLIO. TEXT...ENDTEXT will do the trick just fine as well as allow you to pre-process any of the data like swapping out CRLF with spaces. -- rk -Original Message- From: ProfoxTech On Behalf Of Kurt at VR-FX Sent: Wednesday, October 30, 2019 12:43 PM To: profoxt...@leafe.com Subject: Re: Exporting Tables Hey RK - I was thinking the same thing. Essentially - Gene - you could do the direct export of data - but, to a CSV file. Then, use lo-level file handling to add the memo field onto each line, and, as RK said - make sure to add in the CRLF. -K- On 10/30/2019 7:42 AM, Richard Kaye wrote: > I believe this goes back to dBase compatibility and these commands do the > same thing. > > It's not too hard to roll your own CSV/Tab delimited file in which case you > can keep your memo fields mostly intact. You will need to convert embedded > CRLF in order to keep one record per line. > > -- > > rk > > -Original Message- > From: ProfoxTech On Behalf Of Tracy > Pearson > Sent: Wednesday, October 30, 2019 10:08 AM > To: profoxt...@leafe.com > Subject: RE: Exporting Tables > > Gene, > > I have not seen a difference in the output of the two commands. > > You might want to consider looking at Craig Boyd's post about exporting and > importing from Excel. It doesn't mention Memo fields that I could see. > https://www.sweetpotatosoftware.com/blog/index.php/2008/09/30/using-ex > cel-20 > 07-file-formats-in-vfp-9-0/ > > HTH, > Tracy > > -Original Message- > From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of > Gene Wirchenko > Sent: Wednesday, October 30, 2019 9:58 AM > To: profoxt...@leafe.com > Subject: Exporting Tables > > Hello: > >I am having to do a bunch of data export so have had a closer look at > the commands. > > 1) I am wondering if there is a difference between > COPY TO ... TYPE ... > > and > > EXPORT TO ... TYPE ... > > where the type is XLS or XL5. > > 2) I know that memo columns are not exported so for tables with > them, I am creating a cursor with the memo columns replaced with > C(254) columns. In a few cases, this will result in data being > clipped. Short of programming my exports to use Office Automation, is > there a way around this? (I mean that is not a kludge. For example, > I could create multiple columns each with a piece of the memo, but > that would be horribly ugly.) > > Sincerely, > > Gene Wirchenko > > [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/dm6pr10mb340100c73bce561560e24f6fd2...@dm6pr10mb3401.namprd10.prod.outlook.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.
RE: SWFox 2019 recap
I was not a presenter, like Tracy , but I also had a great time at SWFox. It's a joy to spend time with one's peers learning new (and sometimes old) things, as well as meeting in person with both old and new friends. I would also encourage anyone on this list who still works with the Fox to consider attending next year's conference, which is scheduled for November 12-15, 2020. -- rk -Original Message- From: ProfoxTech On Behalf Of Tracy Pearson Sent: Wednesday, October 30, 2019 12:38 PM To: profoxt...@leafe.com Subject: SWFox 2019 recap I am back to calm after the first day back to work. I had a great time at the conference and hope to stay connected with those I met. I answered an email this morning and thought about the conversation I had with Richard Kaye. Good conversations, good information, and a fun time. I hear I did well as my first time speaking at the conference. Maybe we can get more ProFoxers to go in 2020. See you around! Tracy ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/dm6pr10mb34015a887940020cd84af252d2...@dm6pr10mb3401.namprd10.prod.outlook.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.
Re: Exporting Tables
Hey RK - I was thinking the same thing. Essentially - Gene - you could do the direct export of data - but, to a CSV file. Then, use lo-level file handling to add the memo field onto each line, and, as RK said - make sure to add in the CRLF. -K- On 10/30/2019 7:42 AM, Richard Kaye wrote: I believe this goes back to dBase compatibility and these commands do the same thing. It's not too hard to roll your own CSV/Tab delimited file in which case you can keep your memo fields mostly intact. You will need to convert embedded CRLF in order to keep one record per line. -- rk -Original Message- From: ProfoxTech On Behalf Of Tracy Pearson Sent: Wednesday, October 30, 2019 10:08 AM To: profoxt...@leafe.com Subject: RE: Exporting Tables Gene, I have not seen a difference in the output of the two commands. You might want to consider looking at Craig Boyd's post about exporting and importing from Excel. It doesn't mention Memo fields that I could see. https://www.sweetpotatosoftware.com/blog/index.php/2008/09/30/using-excel-20 07-file-formats-in-vfp-9-0/ HTH, Tracy -Original Message- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Gene Wirchenko Sent: Wednesday, October 30, 2019 9:58 AM To: profoxt...@leafe.com Subject: Exporting Tables Hello: I am having to do a bunch of data export so have had a closer look at the commands. 1) I am wondering if there is a difference between COPY TO ... TYPE ... and EXPORT TO ... TYPE ... where the type is XLS or XL5. 2) I know that memo columns are not exported so for tables with them, I am creating a cursor with the memo columns replaced with C(254) columns. In a few cases, this will result in data being clipped. Short of programming my exports to use Office Automation, is there a way around this? (I mean that is not a kludge. For example, I could create multiple columns each with a piece of the memo, but that would be horribly ugly.) Sincerely, Gene Wirchenko [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/fab97fcc-21f8-7d82-49fe-8c4597e25...@optonline.net ** 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.
SWFox 2019 recap
I am back to calm after the first day back to work. I had a great time at the conference and hope to stay connected with those I met. I answered an email this morning and thought about the conversation I had with Richard Kaye. Good conversations, good information, and a fun time. I hear I did well as my first time speaking at the conference. Maybe we can get more ProFoxers to go in 2020. See you around! Tracy ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/000c01d58f40$5388a280$fa99e780$@powerchurch.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.
Re: Exporting Tables
On Wed, Oct 30, 2019 at 9:58 AM Gene Wirchenko wrote: >1) I am wondering if there is a difference between > where the type is XLS or XL5. > Nope, according to: https://www.tedroche.com/hackfox7/s4g059.html "Both COPY TO and EXPORT copy selected data to another file. We can't see much reason to use EXPORT, since COPY TO can do everything it does and more. (In fact, we're fairly convinced EXPORT exists only because IMPORT does.)" >2) I know that memo columns are not exported so for tables with > them, I am creating a cursor with the memo columns replaced with > C(254) columns. In a few cases, this will result in data being > clipped. Short of programming my exports to use Office Automation, > is there a way around this? (I mean that is not a kludge. For > example, I could create multiple columns each with a piece of the > memo, but that would be horribly ugly.) > For some projects, I created a textmerge file, named it something.CSV and use textmerge to export the PK and commas and text delimiters and the memo fields. Rejoining the two data sources was left as an exercise for the receiver. Be wary of the need to escape text delimiters if used within the memo field, i.e., O'Reilly or "Sold "As Is" " -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/CACW6n4sOwakyP9syC5r4FGJ_poJPQ=uwgf0kpybhqddtqxa...@mail.gmail.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.
Re: Exporting Tables
Gene
If CSV is acceptable to you, you may try the CSVProcessor class at VFPX.
m.CSV = CREATEOBJECT("CSVProcessor")
m.CSV.Export("output.csv")
Whatever memo fields are on your table, they will be exported, as well.
You may also consider using one of the XLSX classes available at VFPX.
On Wed, Oct 30, 2019 at 1:58 PM Gene Wirchenko wrote:
> Hello:
>
> I am having to do a bunch of data export so have had a closer
> look at the commands.
>
>1) I am wondering if there is a difference between
>
>COPY TO ... TYPE ...
>
> and
>
>EXPORT TO ... TYPE ...
>
> where the type is XLS or XL5.
>
>2) I know that memo columns are not exported so for tables with
> them, I am creating a cursor with the memo columns replaced with
> C(254) columns. In a few cases, this will result in data being
> clipped. Short of programming my exports to use Office Automation,
> is there a way around this? (I mean that is not a kludge. For
> example, I could create multiple columns each with a piece of the
> memo, but that would be horribly ugly.)
>
> Sincerely,
>
> Gene Wirchenko
>
>
[excessive quoting removed by server]
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message:
https://leafe.com/archives/byMID/CADj74tG3Jh3pA+uz3ixQNTVD5=4hbxynw7xzgsqtq-rrirr...@mail.gmail.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.
RE: Exporting Tables
I believe this goes back to dBase compatibility and these commands do the same thing. It's not too hard to roll your own CSV/Tab delimited file in which case you can keep your memo fields mostly intact. You will need to convert embedded CRLF in order to keep one record per line. -- rk -Original Message- From: ProfoxTech On Behalf Of Tracy Pearson Sent: Wednesday, October 30, 2019 10:08 AM To: profoxt...@leafe.com Subject: RE: Exporting Tables Gene, I have not seen a difference in the output of the two commands. You might want to consider looking at Craig Boyd's post about exporting and importing from Excel. It doesn't mention Memo fields that I could see. https://www.sweetpotatosoftware.com/blog/index.php/2008/09/30/using-excel-20 07-file-formats-in-vfp-9-0/ HTH, Tracy -Original Message- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Gene Wirchenko Sent: Wednesday, October 30, 2019 9:58 AM To: profoxt...@leafe.com Subject: Exporting Tables Hello: I am having to do a bunch of data export so have had a closer look at the commands. 1) I am wondering if there is a difference between COPY TO ... TYPE ... and EXPORT TO ... TYPE ... where the type is XLS or XL5. 2) I know that memo columns are not exported so for tables with them, I am creating a cursor with the memo columns replaced with C(254) columns. In a few cases, this will result in data being clipped. Short of programming my exports to use Office Automation, is there a way around this? (I mean that is not a kludge. For example, I could create multiple columns each with a piece of the memo, but that would be horribly ugly.) Sincerely, Gene Wirchenko ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/dm6pr10mb340118e9b10819669a565284d2...@dm6pr10mb3401.namprd10.prod.outlook.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.
Re: Exporting Tables
Why not Import from SQL Server or Access? You can then make a backup file from SQL or just copy the access one to give to others who cannot use Fox tables. On Wed, Oct 30, 2019 at 8:58 AM Gene Wirchenko wrote: > Hello: > > I am having to do a bunch of data export so have had a closer > look at the commands. > >1) I am wondering if there is a difference between > >COPY TO ... TYPE ... > > and > >EXPORT TO ... TYPE ... > > where the type is XLS or XL5. > >2) I know that memo columns are not exported so for tables with > them, I am creating a cursor with the memo columns replaced with > C(254) columns. In a few cases, this will result in data being > clipped. Short of programming my exports to use Office Automation, > is there a way around this? (I mean that is not a kludge. For > example, I could create multiple columns each with a piece of the > memo, but that would be horribly ugly.) > > Sincerely, > > Gene Wirchenko > > [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/cajidmyjvw347h3omdf6rai3lpovsrb6atc1grnqy1o4hcqw...@mail.gmail.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.
RE: Exporting Tables
Gene, I have not seen a difference in the output of the two commands. You might want to consider looking at Craig Boyd's post about exporting and importing from Excel. It doesn't mention Memo fields that I could see. https://www.sweetpotatosoftware.com/blog/index.php/2008/09/30/using-excel-20 07-file-formats-in-vfp-9-0/ HTH, Tracy -Original Message- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Gene Wirchenko Sent: Wednesday, October 30, 2019 9:58 AM To: profoxt...@leafe.com Subject: Exporting Tables Hello: I am having to do a bunch of data export so have had a closer look at the commands. 1) I am wondering if there is a difference between COPY TO ... TYPE ... and EXPORT TO ... TYPE ... where the type is XLS or XL5. 2) I know that memo columns are not exported so for tables with them, I am creating a cursor with the memo columns replaced with C(254) columns. In a few cases, this will result in data being clipped. Short of programming my exports to use Office Automation, is there a way around this? (I mean that is not a kludge. For example, I could create multiple columns each with a piece of the memo, but that would be horribly ugly.) Sincerely, Gene Wirchenko [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/000801d58f2b$71e3fc30$55abf490$@powerchurch.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.
Exporting Tables
Hello: I am having to do a bunch of data export so have had a closer look at the commands. 1) I am wondering if there is a difference between COPY TO ... TYPE ... and EXPORT TO ... TYPE ... where the type is XLS or XL5. 2) I know that memo columns are not exported so for tables with them, I am creating a cursor with the memo columns replaced with C(254) columns. In a few cases, this will result in data being clipped. Short of programming my exports to use Office Automation, is there a way around this? (I mean that is not a kludge. For example, I could create multiple columns each with a piece of the memo, but that would be horribly ugly.) Sincerely, Gene Wirchenko ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/ ** 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.
