Search results for query: *

Not something I've played with, but AttachmentSelection looks like it should get you what you need. Maybe show us some code. Tamar

Glad I was able to help. I guess you found the code. For others, the downloads for each session on my site are linked at http://tomorrowssolutionsllc.com/conferencepapers.php. Tamar

I didn't cover exactly this situation, but in this paper (http://tomorrowssolutionsllc.com/ConferenceSessions/Drag%20Your%20Applications%20into%20the%2021st%20Century.pdf), I wrote about dragging from Outlook into VFP. Look for the section titled "Dragging from Outlook". Tamar

Do a lot of people really leave VFP running for days at a time? I shut it every time I'm done with it. Of course, I also shut down my development computer (which is a desktop) every night. Tamar

If I remember right, the parenthesis (name expression) notation came in VFP 5. It may be that the code you're showing from KiloFox is older than that. I wrote at length about macros and name expressions and other related stuff here...

I think EinTerraner has given you what you need. I agree with his question about why you are creating a temporary table rather than just using a cursor. Tamar

A few comments to make your code stronger. 1) Don't refer to work areas by number. To find an available work area, use: SELECT 0 2) Once you have a table open, always refer to it by its alias. For example: SELECT Clientes When you do this, you never have to know the work area number...

There are lots of ways to do this. If you don't mind moving the record pointer in that table: LOCATE FOR NOT knjizeno IF FOUND() * Don't allow the user to continue ENDIF or: COUNT TO nFalse FOR NOT knjizeno IF nFalse > 0 * Don't allow the user to continue ENDIF You could also use a...

Just pointing out a minor typo in Mike's code that would give you trouble in a cut-and-paste. Should be: loWord = CREATEOBJECT("word.application") Tamar

Is Word actually installed on the machines where you're having a problem? Not the Click to run or Office 365 version? Tamar

I don't think you can check the enabled status of a control in FoxPro 2.6. That said, I haven't had to write FP2.6 code for 25 years or so, so maybe I've just forgotten. Tamar

The point is that it's the user's computer and the user should be able to control that stuff. Most essentially, when a user has some visual impairment (including color blindness, which is pretty common), they MUST be able to override the programmer's choices, or the application may be unusable...

I do NOT recommend using separate IDX files to keep the CDX small. IDXs are not updated when you modify the data unless you explicitly open them beforehand. The addition of the CDX (in FoxPro 2.0, I think) was a great change, as it reduced the chance of indexes getting out of sync dramatically...

I just want to point out that you should not use a macro in this query. A name expression is faster and, more importantly, works even if the file name/path contains any spaces. (I know that's not an issue the way you're doing it, but make it a habit to use name expressions rather than macros...

Chris had a small typo in one of his links. It should be https://github.com/VFPX/nfJson. I think you'll find that tool lets you convert JSON to a cursor very easily. Tamar

Thanks, Mike. I guess I knew that was there, but never thought about using it. Just added your first three, which are all topics I visit often. Tamar

I cannot urge everyone strongly enough to use the Toolbox rather than the Form Controls toolbar. It makes all this stuff so much easier. I wrote about it here: http://tomorrowssolutionsllc.com/ConferenceSessions/Making%20the%20Most%20of%20the%20Toolbox.pdf and here...

I just want to add to Chriss's detailed answer that anytime you want to break up something that's regular, try ALINES() first. So, for example, if you have a line of data separated by commas, use ALINES() and specify "," as the separator. There are times you need StrExtract() because you're...

Just want to add that putting controls inside containers is way easier if you use the Toolbox instead of the toolbar. (In my view, pretty much everything about constructing forms is easier with the Toolbox.) I've written about this...

Filip, your mentor is wrong here. If there is any possibility that more than one person will be using this application at the same time, finding the largest value and incrementing it is dangerous, because two people could do that at the same time, and you'd end up with two records with the same...