Error 2176
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring runtime error 2176 developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question
Security Error 2176
x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join
Filereference Error 2176
them; it only takes a minute: Sign up Should I workaround Flex security error 2176 up vote -1 down vote favorite I got the following error: Error #2176: Certain actions, such as those that display a pop-up window, may only
Actionscript Error 2176
be invoked upon user interaction, for example by a mouse click or button press. I found a similar thread here and the short explanation of the problem is: Adobe does this as a sort of security measure to ensure users are the ones messing with files rather than potentially harmful code However this thread doesn't answered my questions and that's why I am asking here: 1) Is there a good reason for me getting this error and is it securityerror error #2176 really a security issue (and if so - maybe I shouldn't workaround it?). 2) What are the potential consequences if I do my workaround (I am asking because obviously Adobe decided that it shouldn't be workaround-ed) actionscript-3 security flex share|improve this question asked May 23 '14 at 11:31 s-rusev 85110 1 We don't have many clairvoyants over here, you'll have to show what you are doing to receive that error in the first place, and explain how you're planning to workaround it. –ndm May 23 '14 at 11:39 I will use the workaround with the two event listeners for the events MOUSE_DOWN and MOUSE_UP mentioned in the other thread. I am getting the error when I manually dispatch an MouseEvent.CLICK on a button that invokes action that goes trough the files. Maybe I wasn't clear enough - my concern is whether it is a good idea to workaround something that obviously isn't supposed to be workaround-ed and how this can do any harm. –s-rusev May 23 '14 at 12:02 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote accepted No, don't try to work around it. Flash isn't allowed to download arbitrary files to your hard drive for some very good reasons. Instead, just use FileReference.download(). The Adobe docs talk more about it. Then you can trigger the download on the user's click. share|improve this answer answer
ElementsAdobe Dreamweaver Adobe MuseAdobe Animate CCAdobe Premiere ProAdobe After EffectsAdobe IllustratorAdobe InDesignView all communitiesExplore Menu beginsMeet the expertsLearn our productsConnect with your peersError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn filereference save 2176 JavaScript back on and reload this page. Please enter a title. You can error 2176 flash not post a blank message. Please type your message and try again. More discussions in ActionScript 3 All CommunitiesAdobe Animate error 2176 access CC - HomeActionScript 3 2 Replies Latest reply on Feb 6, 2011 3:52 PM by icecappacino SecurityError: Error #2176 icecappacino Feb 6, 2011 11:33 AM Hey guys,I'm using AS3 and the FB Graph http://stackoverflow.com/questions/23828089/should-i-workaround-flex-security-error-2176 API to upload bitmap data to facebook. However,on a MouseEvent.CLICK event I get the following errorSecurityError: Error #2176: Certain actions, such as those that display a pop-up window, may only be invoked upon user interaction, for example by a mouse click or button press.at flash.net::URLStream/load()at flash.net::URLLoader/load()at com.facebook.graph.net::FacebookRequest/loadURLLoader()[D:\Work\cartoon\com\facebook\grap h\net\FacebookRequest.as:372]
This is weird because it was triggered by an onclick. In psuedo codeuser clicks uploadI encode datawhen this is finish https://forums.adobe.com/thread/787945 I send to facebook apiI guess I should note that the encoding process also triggers and event and passes tru several steps again before reaching the facebook apiIs there anyway to keep the mouse event within the calls stack? I have the same question Show 0 Likes(0) 3380Views Tags: none (add) This content has been marked as final. Show 2 replies 1. Re: SecurityError: Error #2176 kglad Feb 6, 2011 11:55 AM (in response to icecappacino) copy your real code that executes your pseudo-code steps. Like Show 0 Likes(0) Actions 2. Re: SecurityError: Error #2176 icecappacino Feb 6, 2011 3:52 PM (in response to kglad) Well,I did some tinkering and re-scripted my code...There were a couple of other events being triggered after the mouse event. I guess this put the click event out of scope. So I now do it in a 2 steps using mouse events for each step. Seems to have solved the problem. Like Show 0 Likes(0) Actions Go to original post Actions More Like This Retrieving data ... Legend Correct Answers - 10 points © 2016 Adobe Systems Incorporated. All Rights Reserved. | Powered by Help | Terms of Use | Privacy Politoo long If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing http://www.dbforums.com/showthread.php?789670-Runtime-error-2176-The-setting-for-this-property-is-too-long messages, select the forum that you want to visit from the selection below. Results 1 to 3 of 3 Thread: Runtime error 2176 The setting for this property is too long Tweet Thread Tools Show Printable Version https://bytes.com/topic/access/answers/955634-vba-access-run-time-error-2176-setting-property-too-long Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 05-19-03,19:02 #1 Sia View Profile View Forum Posts Registered User Join Date Dec 2002 Location Washington D.C. Posts error 2176 164 Unanswered: Runtime error 2176 The setting for this property is too long Hi, I have a form which has a couple of text boxes. The text boxes are bound to a SQL Server table with Varchar (8000) Data type. Due to the fact that there is a long text in each control box, I have created a Zoom functionality. I have crated a new Text box control named ZText (unbound) which is invisible until runtime error 2176 the zoom button is clicked. After the user clicks the Zoom button, the Ztext control box becomes visible on the form which is larger than the original one. Then I put the text from the original control box (IssueTxt) to the Zoom one. It works so far and the user can view the contect in a larger box. But the problem is when I want to save the edits (if any). When I want to set the orginal text box to the new, if the text is long I get the following error: Runtime error 2176,The setting for this property is too long Here is the code I use for save: Private Sub SEdit_Click() DoCmd.RunCommand acCmdSaveRecord Dim text As String Me!Ztext.SetFocus text = Me!Ztext.Text Me!IssueTxt.SetFocus Me!IssueTxt.Text = text Me!Ztext.Visible = False Me!SEdit.Visible = False Me!close.Visible = False Me!YBox.Visible = False End Sub any ideas what the problem could be? The intellect is better than desire, for the intellect makes you a king over your destiny, and desire makes you a slave of your destiny. Reply With Quote 11-19-04,17:51 #2 FastAl View Profile View Forum Posts Registered User Join Date Nov 2004 Posts 1 Sia, Late relpy, yes, but here's the solution: use the .Value property instead of the .Text property. Pitfall for VB programmers!!! _______________________ Follow Christ. Cheat Death. Reply With Quote 11-20-
too long + Ask a Question Need help? Post your question and get tips & solutions from a community of 418,509 IT Pros & Developers. It's quick & easy. VBA Access: Run-time Error '2176'-The setting for this property is too long P: 4 Prithvi Ragu There is an access database table called DemoImageT with a field called Image to store images (using OLE Objects). It has another field called ID which is a text field. It has values 1,2,3..etc. I have an Image holder called ImageBox1 in an Access form. When a button is clicked I want to display the image stored in the table in the image holder on the form. I executed a query and stored the results in a recordset. Then I set the picture property to the retrieved image. My code was: Expand|Select|Wrap|Line Numbers DimmyConnection1AsADODB.Connection DimmyRecordSet1AsNewADODB.Recordset SetmyConnection1=CurrentProject.AccessConnection SetmyRecordSet1.ActiveConnection=myConnection1 myRecordSet1.Open"SELECT*FROMDemoImageTWHEREID='1'" IfIsNull(myRecordSet1.Fields(1))=FalseThen MsgBox("Imagepresent") ImageBox1.Visible=True ImageBox1.Picture=myRecordSet1.Fields(1) Else MsgBox("Noimage") EndIf I get the message box Image present. But then I get: run time error 2176- The setting for this property is too long. The error occurs in the line: Expand|Select|Wrap|Line Numbers Me.ImageBox1.Picture=myRecordSet1.Fields(1) Is there something wrong with the code? Is there any other way to retrieve images stored in an Access database using VBA and display it on a form? If the above method is correct, what might be wrong? Mar 24 '14 #1 Post Reply ✓ answered by zmbd OK, One really should avoid using the OLE to store the pictures, it creates alot of bloat... So, when all things look bad, I go back to the Northwinds example database, I was originaly going to look at the 2003 version; however, you've said you are using ACC2010 so I thought I'd take a look at the newer versions. Looking at the 2007 version, it appears that MS has actually done something worth while - the attachment field data type. >NOTE> If you use this field upsizing later more than likely will result in some headaches, loss of sleep, the desire to bang one's head against the wall, and huge amounts of caffin