Re: updating 2 forms

On 2016-07-06 17:01, Ted Roche wrote: On Wed, Jul 6, 2016 at 4:51 PM, Edward Leafe wrote: I know I've said it, and I know Ted's said it, and so have many others. It is excellent advice. 'Tis. I'm pretty sure I learned it from Steven Black, who 'got' OOP long before I did.

Re: updating 2 forms

On 2016-07-06 16:51, Edward Leafe wrote: On Jul 6, 2016, at 2:09 PM, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote: This tip below reminds me of that phrase years ago by Ed or Ted or somebody else that said "program to the interface, not the implementation." I know I've said it, and I

Re: xBASE Appending from a Cursor

On Wed, 06 Jul 2016 15:57:20 -0700, Gene Wirchenko wrote: >Hello: > > I ran into some trouble writing an update program for my >app. Having not done it for quite a while, I forgot how to xBASE >append from a cursor. A simple > append from thecursorname >does

xBASE Appending from a Cursor

Hello: I ran into some trouble writing an update program for my app. Having not done it for quite a while, I forgot how to xBASE append from a cursor. A simple append from thecursorname does not work. Instead, I finally remembered the, rather less-than-obvious

RE: updating 2 forms

"Program to an interface, not an implementation" is the first principle espoused by the Gang of Four (Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides) in their 1995 book (and OOP bible), Design Patterns: Elements of Reusable Object-Oriented Software. So I think a lot of us have said

Re: updating 2 forms

On Wed, Jul 6, 2016 at 4:51 PM, Edward Leafe wrote: > On Jul 6, 2016, at 2:09 PM, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote: > >> This tip below reminds me of that phrase years ago by Ed or Ted or somebody >> else that said "program to the interface, not the

Re: updating 2 forms

On Jul 6, 2016, at 2:09 PM, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote: > This tip below reminds me of that phrase years ago by Ed or Ted or somebody > else that said "program to the interface, not the implementation." I know I've said it, and I know Ted's said it, and so have many

RE: Do prompt when starting EXE

Thanks Mike, I will check this out also. We can't test again till the morning when they let us back on their computers. -Original Message- From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Michael Glassman Sent: Wednesday, July 6, 2016 4:25 PM To: profox@leafe.com Subject:

RE: Do prompt when starting EXE

Kent, Christof's suggestion reminded me that Windows' own security settings can cause this behavior as well. Launch Internet Options (from either the run box, the networking center, or the tools menu in Internet Explorer). Click on the Security tab, select Local intranet, click Sites, and click

Re: updating 2 forms

This tip below reminds me of that phrase years ago by Ed or Ted or somebody else that said "program to the interface, not the implementation." Alan's example was very good and not cluttered. On 2016-07-06 09:50, rafael copquin wrote: I would do it this way: On your first form, put a button

RE: Do prompt when starting EXE

Hello Christof, Thanks, I had not thought about a virus scanner. We have the program working fine when mapped to the regular R: drive but they created a new Q: mapped drive with a copy of the folder that is working. This new Q: mapped drive is the one that has the problem. We get the same Do

RE: Do prompt when starting EXE

I think Christof gave you some good pointers. -- rk -Original Message- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Kent Belan Sent: Wednesday, July 06, 2016 2:45 PM To: profoxt...@leafe.com Subject: RE: Do prompt when starting EXE Thanks for the info. I checked

RE: Do prompt when starting EXE

Thanks for the info. I checked and there is a config.fpw built into the project but it is very basic and should not cause this problem. No other config.fpw files were found. Here is the config.fpw file that is in the project: RESOURCE=OFF SCREEN=OFF EDITWORK="C:\TEMP\" PROGWORK="C:\TEMP\"

Re: Do prompt when starting EXE

> > I have an VFP 9 EXE that runs fine on mapped drive on the network from the > main folder. They made a copy of the folder and a new mapped drive to the > new folder but when we try to start the EXE we get a DO prompt. We can > select the EXE at this point and the program will start. Very weird.

RE: Do prompt when starting EXE

Maybe a config.fpw pointing somewhere else? -- rk -Original Message- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Kent Belan Sent: Wednesday, July 06, 2016 12:17 PM To: profoxt...@leafe.com Subject: Do prompt when starting EXE Hello, I have an VFP 9 EXE that runs

Re: [OT] Happy Fourth of July et al

At 18:41 2016-07-05, "Ken Kixmoeller (ProFox)" wrote: I'm sure you mean "Independence Day" (we don't say "Happy November 24th!") No, I meant "Fourth of July". The term is used by many as a Web search will show you. You might also clean

Do prompt when starting EXE

Hello, I have an VFP 9 EXE that runs fine on mapped drive on the network from the main folder. They made a copy of the folder and a new mapped drive to the new folder but when we try to start the EXE we get a DO prompt. We can select the EXE at this point and the program will start. Very weird.

RE: updating 2 forms

If the second form isn't modal, you'll need to account for dangling references. I suspect it will be modal. If not let us know. Tracy Pearson PowerChurch Software ___ Post Messages to: ProFox@leafe.com Subscription Maintenance:

Re: updating 2 forms

I would do it this way: On your first form, put a button to call the second form. In the button's click event do this: do form secondform with thisform On the second form init event: lparameters toForm thisform.oForm = toForm (you created a property called oForm in the second form and

Re: updating 2 forms

I can email you a little demo project if you like. -- Alan Bourke alanpbourke (at) fastmail (dot) fm ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list:

Re: updating 2 forms

This is a good example of why you should use form classes. Have your parent form class 'frmParentForm' and have a method called SetTextBox() on it which takes a string. Also have your button to launch your child form. SetTextbox() code: lparameters lcString thisform.textbox1.value = lcString

Re: updating 2 forms

Maybe something like this :- do form Form1 name FIRSTFORM This form has text1 object When you run the second form As you enter the text in the textbox object, in the interactivechange method :- FIRSTFORM.text1.value = this.value FIRSTFORM.text1.refresh Is that what you are thinking of ? On