I am trying to export kendo grid data in excel format but getting an error. Here's the image:
I think it would be pretty clear with the picture as to what the error is. What could I be missing here?
The Excel functionality was not introduced until version 2014.3.1119(released Nov. 19, 2014). You will have to update to at least that version to have access to .Excel().
Related
I'm trying to automate the updating of some GANTT bars with a button setting the beginning date at 2w before now and ending date at 10w after now.
Problem is that it actually work and changes the data for the shape but doesn't update the visual. When I right click on the shape, open the parameters modification, select then unselect any parameter and validate, it actually update the visual, without any modification.
Do someone have an idea why this happen ?
I haven't found anywhere the same problem on internet except on a topic 19 yo with no response.
I'm using
Application.ActiveWindow.Page.Shape.ItemFromID(myID).CellsSRC(visSectionUser, 1, visUserValue).FormulaU = "NOW() -14ed"
Application.ActiveWindow.Page.Shape.ItemFromID(myID).CellsSRC(visSectionUser, 2, visUserValue).FormulaU = "NOW() + 10ew"
also tried with FormulaForce.
Thanks for any help
Gantt chart diagrams are controlled by an addin that is built-in to Visio. This addin controls most aspects of the diagram and Microsoft don't publish details of its internals. Looking at the Actions cells you can see that the Edit Date command performs action:
RUNADDONWARGS("GC","/CMD=2610")
This might do all kinds of things internally.
Good luck.
if you're working with Views and SQL Server Management Studio (i'm using version 14)
then you probably have noticed it, the code you put in the view designer gets auto formatted
i personally think that the way of formatting is really ugly, especially that JOIN statements are always at the end of the line. however, i'd like to change that.
i already looked a bit up and i know we can install custom formatters, but they only work for sql files (like new queries) but that won't overwrite the default behaviour of the view designer
can anyone help me find a solution? i don't care whether it is downloading a tool or it would be already helpful if i could at least stop the auto formatting somehow so i can at least apply my own code style and then it's the same for everyone in the team
i highly hope you know any kind of approach here.
thank you!
You cannot change the formatting being applied for DESIGN. Even in the new version of SSMS, I see that the code is formatted little differently in view designer. Even if you change through designer and save it and open it again, it is not keeping formatting changes and applies its formatting changes, when you open it again through View Designer.
You can try the below approach:
Right click the view and open in new window
Now, you can apply formatting manually or you can any of the SQL formatting tools or corresponding SSMS add-on to formatting to the code. Now, the formatting will be kept intact if you open it again. Sql formatting tools
Today, VS 2017 Community Edition recommended I take a small update, which I did.
Now any VB.NET solution that I open shows a blank form (as if adding a new form). However, in examining the files, all of the controls and the associated code are present in the files. It just appears that the VB.NET Form Designer is not happy with something in a file.
Is there anything I can do to kick the Form Designer to display the form correctly or is there anything I can examine to ascertain some specific error it might be throwing so that I can look in the right place for resolution.
I figured it out and thought the solution might be useful for others. For some reason, the new version was converting every VB Form control from this (for example) Me.labelFrequency.Location = New System.Drawing.Point(113, 197) to this Me.labelFrequency.Location = New System.Drawing.Point(-32768, 197)(Note the italicized invalid coordinate). It did this for EVERY control in the project. The negative coordinate was throwing off the Designer (obviously). I cleared the VSTS cache and restored a version of the xyzzy.Designer.VB file with the correct values and it stopped doing this. Left this here in case anyone else found this useful.
I've recently upgraded my project to Visual Basic 2008 and I'm getting the following errors which I cannot identify, I hope someone can help:
AxThreed.AxSSCommand is not defined
AxActiveInput.AxSSDropDownEdit is not defined
AxPVTEXT3DLib.AxPVText3D is not defined
Any idea what this is and how to fix it?
It looks these are references to 3rd Party ActiveX controls. ActiveThreed, Protoview Date Control, etc
You may need to Add/Re-Add the relevant control to your project. Right click on the toolbox so select the items to want to use. If you don't see them in the list to may need to register/re-register them on that machine
Have a look at this page for more info: http://msdn.microsoft.com/en-us/library/ms973200.aspx
Number 3 here seems to indicate how to fix the problem... I believe some of your controls are not loading.
since yesterday I´m getting "document is not under source control" when clicking on a nib file in the navigator. And instead of the graphical presentation I see xml.
I´ve been using the current version 4.3.2 (4E2002) since March 21st 2012. But this error came up first yesterday night. Restarting and cleaning the project didn´t help and restarting the mac didn´t help either. When switching to another project, I don´t have that problem. I´m not aware that I changed any preferences.
Any clues what´s wrong?
Greetings from Switzerland, Ronald Hofmann
Solution
I found what was wrong: 'Show the version editor' was turned on.
When turning it off the error is gone.
Ronald
Try control-clicking on the nib file in the navigator and then go to "Open-As" and select Interface Builder - iOS. That should clear up your problem with it displaying as XML.
As far as it being under source control, is your project as a whole under source control? If so, what are you using?