BUG: "Open With" always opens default application after allowed

[Guest]

When I click on "Open With" on a File that's controlled by MSAS (such as .vb
files) to open it in NotePad, MSAS asks me if I want to allow it. If I click
no, it's not opened. If I click yes it's not opened with the program I wanted
to open it, but with the application that is linked to this file extension.

In the Thread: "Open With problem" the answer was to change the registration
of the file type. That can't be the solution. I would have to change it back
thenafter to the original application. If this application is using classes
instead of filetypes that's not easy to solve and requires deep understanding
of the registry. The solution for this bug /must/ be opening the file with
the application I selected in the "Open With" Explorer context menu.

 

[Bill Sanderson]

I suspect that the solution to this issue, with the current beta1 code, is
to turn off the checkpoint that does script checking. It's buggy, and I
think that the behavior you are describing is part of the bugginess.

I haven't tested to see whether that's enough to do the job--I'm not sure
that I know how to do that--I don't have any regular processes that use
scripting on my home machine.

I agree with you that this is a bug, and a significant issue, and that
changing the file association is not the way to fix it.

 

[Henry Habermacher [MVP Access]]

Hi Bill

quoting Bill Sanderson:

I agree with you that this is a bug, and a significant issue, and that
changing the file association is not the way to fix it.

It's even more significant as I for example want to change the script itself
using notepad and after giving MSAS the allowance to open it, it will
execute it and not open it in Notepad what may result in a loss of data (if
there is code - that I want to change with my action - inside that changes
or even deletes data).

Henry

 

[Henry Habermacher [MVP Access]]

Just to clarify why it's dangerous:

1. Create a new text-file

2. Add following line of code into this file:
msgbox "Hello World"

3. rename it to test.vbs

4. Right-Click on the VBS file and select Open With ... Notepadd

5. Give MSAS the allowance to open the file

==> A msgBox apears telling me "Hello World"

If this would have been a virus or spyware It would have been installed now
also I only wanted to have a look at it's content! Seems to be a really
very, very dangerous bug as the script was granted to run, not to open in
NotePad as expected.

Henry



quoting Henry Habermacher [MVP Access]:

Hi Bill

quoting Bill Sanderson:

It's even more significant as I for example want to change the script
itself using notepad and after giving MSAS the allowance to open it,
it will execute it and not open it in Notepad what may result in a
loss of data (if there is code - that I want to change with my action
- inside that changes or even deletes data).

Henry

--
Keine E-Mails auf Postings in NGs senden!
Don't send e-mails to postings in newsgroups!
KB: http://support.microsoft.com/default.aspx
FAQ: http://www.donkarl.com (neu mit Suchfunktion!)
OH: Online Hilfe von Microsoft Access (Taste F1)
Downloads: http://www.dbdev.org

 

[Bill Sanderson]

I agree---that's why I mentioned turning off the checkpoint that deals with
scripting as the best fix. There are a number of serious bugs in this
process. In fact, there was, for a time, a "Scripting Guys" article on
Microsoft's site about these issues. However, it was pulled and the content
is no longer available. I find that action quite puzzling, since nothing
corresponding was done for the beta to fix these issues--they simply removed
the only published guideance we could point to about the problems.

--

Just to clarify why it's dangerous:

1. Create a new text-file

2. Add following line of code into this file:
msgbox "Hello World"

3. rename it to test.vbs

4. Right-Click on the VBS file and select Open With ... Notepadd

5. Give MSAS the allowance to open the file

==> A msgBox apears telling me "Hello World"

If this would have been a virus or spyware It would have been installed
now also I only wanted to have a look at it's content! Seems to be a
really very, very dangerous bug as the script was granted to run, not to
open in NotePad as expected.

Henry



quoting Henry Habermacher [MVP Access]:

Hi Bill

quoting Bill Sanderson:

It's even more significant as I for example want to change the script
itself using notepad and after giving MSAS the allowance to open it,
it will execute it and not open it in Notepad what may result in a
loss of data (if there is code - that I want to change with my action
- inside that changes or even deletes data).

Henry

--
Keine E-Mails auf Postings in NGs senden!
Don't send e-mails to postings in newsgroups!
KB: http://support.microsoft.com/default.aspx
FAQ: http://www.donkarl.com (neu mit Suchfunktion!)
OH: Online Hilfe von Microsoft Access (Taste F1)
Downloads: http://www.dbdev.org