Hello Claudine, The two options are there for a reason. One option allows you to quickly view the document using the R:Base PDF browser and once you exit, the file is closed. The other option allows you to see the document using Acrobat Reader and it has a lot more option and allows you to keep the file open; however, when a file is open it cannot be deleted. I believe there is now a command that allows you to check if the file is open and if it is indeed open, you can display a message asking the user to close the file before it can be deleted. Hopefully this explains the use of the two buttons…as you know we can always do things in more than one way and it is nice for the user to have options. Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 From: rbase-l@googlegroups.com [mailto:rbase-l@googlegroups.com] On Behalf Of Claudine Robbins Sent: Friday, February 03, 2017 5:29 PM To: rbase-l@googlegroups.com Subject: RE: [RBASE-L] - ERASE filespec Buddy, et al… and Javier, I think I have figured it out. The files in question are pdfs. I’m using a form Javier created and it has two “viewing” button options for the pdf file being viewed and replaced, one to view in Adobe Reader and one to view in PDF viewer. I wondered about that Javier but never asked… This afternoon, after finding out online that pdfs cannot be overwritten after being opened because the system sees them as being “in use” (indeed, sometimes there are multiple tabs in the Adobe reader, so they do stay active), I tested using the PDF viewer button in my form. And guess what, that works reliably, every time… So thank you to everyone who tried to help me figure this out. And, most of all, thank you Javier! Claudine J From: rbase-l@googlegroups.com [mailto:rbase-l@googlegroups.com] On Behalf Of Claudine Robbins Sent: Friday, February 03, 2017 3:41 PM To: rbase-l@googlegroups.com Subject: RE: [RBASE-L] - ERASE filespec Nothing works so I’m just going to wait until next Wednesday and see if a new Windows Update isn’t released to fix whatever the problem is. I’m experiencing the same behavior on the cloud server too… From: rbase-l@googlegroups.com [mailto:rbase-l@googlegroups.com] On Behalf Of Alastair Burr Sent: Friday, February 03, 2017 6:33 AM To: rbase-l@googlegroups.com Subject: Re: [RBASE-L] - ERASE filespec I think, "technically" you DELete records from a database and ERASE files from the directory/folder.
I usually make sure that I have the DOS command correct and then in R:Base create a variable & activate that: SET VAR vEraseFile TEXT = 'ERASE C:\Temp\*.*' &vEraseFile and SET VAR vEraseFile TEXT = 'ERASE "C:\Temp\Folder with spaces\*.*" ' Regards, Alastair. On 02/02/2017 20:24, Claudine Robbins wrote: Thanks Dan and Buddy, ERASE or DELETE get the same result. No spaces in filename2. Both filename1 and filename2 are UNC. Commands work at R:> prompt… From: rbase-l@googlegroups.com [mailto:rbase-l@googlegroups.com] On Behalf Of Buddy Walker Sent: Thursday, February 02, 2017 2:01 PM To: rbase-l@googlegroups.com Subject: RE: [RBASE-L] - ERASE filespec Sorry send button to easy to hit J If the filename2 contains spaces then you will need to enclose in filename2 in quotes. Buddy From: rbase-l@googlegroups.com [mailto:rbase-l@googlegroups.com] On Behalf Of Claudine Robbins Sent: Thursday, February 2, 2017 2:36 PM To: rbase-l@googlegroups.com Subject: [RBASE-L] - ERASE filespec Hello all, I’m having a bit of a headache with an ERASE filespec command which has worked reliably for weeks, works reliably from the R:> prompt and yields “Failed deleting… (2262)” then “Cannot create destination file (2086)” from within a form when I: ERASE .filename2 And COPY .filename1 .filename2 Permissions are ok… Undoubtedly my fault but I can’t find it, help! TIA, Claudine -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to rbase-l+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
