It is OK to start with LegalZoom but pay an attorney to look the document over. He should not charge for more than an hour, perhaps less.
If you ever need the protection of an LLC, you want to be sure it is solid. Wes Wilson Wes Wilson, President ERW Custom Programming, Inc. Crescent Lake Plaza 5459 Elizabeth Lake Rd. Waterford, MI 48327 (248) 683-4182 www.erw.com weswil...@erw.com ________________________________ From: "profox-requ...@leafe.com" <profox-requ...@leafe.com> To: profox@leafe.com Sent: Friday, August 9, 2013 11:08 AM Subject: ProFox Digest, Vol 124, Issue 8 ----- Forwarded Message ----- Send ProFox mailing list submissions to profox@leafe.com To subscribe or unsubscribe via the World Wide Web, visit http://mail.leafe.com/mailman/listinfo/profox or, via email, send a message with subject or body 'help' to profox-requ...@leafe.com You can reach the person managing the list at profox-ow...@leafe.com When replying, please edit your Subject line so it is more specific than "Re: Contents of ProFox digest..." Today's Topics: 1. [NF] Looking at a potential Glass app (Stephen Russell) 2. RE: keypress and hotkeys (Tracy Pearson) 3. Re: keypress and hotkeys (Rafael Copquin) 4. Re: FoxPro, Windows 8 and Office Automation? -SOLVED (Ted Roche) 5. Re: keypress and hotkeys (Tracy Pearson) 6. Re: FoxPro, Windows 8 and Office Automation? -SOLVED (Jeff Johnson) 7. system set up (Sytze de Boer) 8. LLC and consulting (James Harvey) 9. Re: FoxPro, Windows 8 and Office Automation? -SOLVED (Ted Roche) 10. Re: LLC and consulting (Kurt @ VR-FX) 11. Re: LLC and consulting (Jeff Johnson) 12. Re: LLC and consulting (Ted Roche) 13. Re: LLC and consulting (Kurt @ VR-FX) 14. Re: Report Properties Multiple Selection (Peter Cushing) 15. RE: system set up (Tracy Pearson) 16. Re: keypress and hotkeys (Rafael Copquin) 17. Re: [NF] Google Calendar API (Ed Leafe) 18. Re: [NF] Google Calendar API (Alan Bourke) Anyone know where the heck within Google I would start to identify the Glass Group? Looking to do two projects. Warehouse / forklift drivers see the pull list and read a lot bar-code off the shipping container that they pull. We pass that back to ERP system for generating Quality report of Certificate of Analysis depending on contract with customer. Other project is for maintenance crew who do inspection runs and have to photograph various aspects of the plant's machinery or raw material supply lines. This year we are beefing up the WiFi to do this type of thing. Just attempting to identify a statement of scope for these potentials. Anyone else thinking that they could find a use for Glass in data collection or input? -- Stephen Russell Sr. Analyst Ring Container Technology Oakland TN 901.246-0159 cell --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- Rafael Copquin wrote on 2013-08-08: > Again with hot key blues!:-( > > I have this form with a grid and a series of hot key calls from the > keypress event of one of its columns (the textbox of the column) > > All goes well, until I change the underlying cursor of the grid. > The hot keys no longer work > > IOW, I use a select statement to show a cursor in the grid. The hot > keys work. Then I use another select statement to populate the grid. > And now the hot keys do not work any more > > Why? > > Please help! > > Rafael Copquin > Rafael, Behind the scene, the grid is being rebuilt. This sudo-code is how I now change grid data. Create a cursor, attach it to the grid. Select into tempCursor Select gridCursor Append from dbf("tempCursor") Use in Select("tempCursor") I've seen odd behavior with another common way, though I don't recall what the specifics were off the top of my head. Grid.recordsource = "" Select ... Grid.recordsource = "gridCursor" Tracy Pearson PowerChurch Software I know that, I have been doing that for years. I even teach VFP to newbies and that is one of the first things they learn But you know what, I _forgot_ to kill the recordsource prior to changing the underlying cursor. Gosh!! You guys call this "brain fart" right? Well, I guess I had one today. Thank you Fred and Stacey, you cleared the fog in my brain :-) Rafael Copquin El 08/08/2013 05:50 p.m., Fred Taylor escribió: > It's called "grid reconstruction". What you've done is destroy all the > code that went with the grid. You may be able to stop that behavior by > blanking the grid.RecordSource property, getting the new data via SQL, and > then resetting the grid.RecordSource property to your new alias for the SQL > cursor. Even if they're the same name, you still have to do this. You may > also need to reset your Column.ControlSource property of all your columns > if your fields in the grid or in any order other than what the fields in > the cursor are. > > > Fred > > > On Thu, Aug 8, 2013 at 1:44 PM, Rafael Copquin > <rcopq...@fibertel.com.ar>wrote: > >> Again with hot key blues!:-( >> >> I have this form with a grid and a series of hot key calls from the >> keypress event of one of its columns (the textbox of the column) >> >> All goes well, until I change the underlying cursor of the grid. >> The hot keys no longer work >> >> IOW, I use a select statement to show a cursor in the grid. The hot keys >> work. >> Then I use another select statement to populate the grid. And now the hot >> keys do not work any more >> >> Why? >> >> Please help! >> >> Rafael Copquin >> >> ______________________________**_________________ >> Post Messages to: ProFox@leafe.com >> Subscription Maintenance: >> http://mail.leafe.com/mailman/**listinfo/profox<http://mail.leafe.com/mailman/listinfo/profox> >> OT-free version of this list: http://mail.leafe.com/mailman/** >> listinfo/profoxtech <http://mail.leafe.com/mailman/listinfo/profoxtech> >> Searchable Archive: >> http://leafe.com/archives/**search/profox<http://leafe.com/archives/search/profox> >> This message: http://leafe.com/archives/**byMID/profox/52040320.1040005@** >> fibertel.com.ar<http://leafe.com/archives/byMID/profox/52040320.1040...@fibertel.com.ar> >> ** 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. >> > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > --- >[excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/1376061312.36641.yahoomail...@web140201.mail.bf1.yahoo.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.
