Here is an example of the Entity I wish to include. I have thought about dropping it into Visio as an Image, but I would like to retain the flexibility of keeping it as an embedded excel table, whilst making use of Visio's cardinality connectors. Thanks for any assistance.
Unless I'm missing the point, the answer is trivial.
Insert the table as OLE object.
Copy the range in Excel, switch to Visio, paste special - excel.
If you want to glue connectors to the table, I better draw according connection points on the shape.
There are many other ways of drawing a table, but this one is certainly the simplest.
Related
I have two excel tables. One is a list of names with a calendar that tracks number of days traveled and puts it in percentage. The other table shows proposed travel schedules for the same list of people but in a different format. I have to manually find their percentage in table 1 and input them to the second table for presentations. I want to develop something that reads the names in both tables and can copy their travel time percentage into the second chart. Maybe adding it in the cell or to a blank row below. I have been unable to find any previous threads relating to this. I am new to programing and do not know if this can be done in VBA macro for excel. Does anyone know what functions I could use to accomplish this?
The quickest way is to use powerpivot. You'll have to look at your version of excel to see how to access it. For instance, powerpivot is included and preset in excel 2016, and is a free add-on you'll need to download for excel 2010.
You can uplaod both those tables into the powerpivot model, define the relationship between the two tables (as simple as dragging the relationships in a diagram view). Then you literally have a pivot table that connects both and you can create a measure that does what you're saying. The plus is that there's so much more you can do!
Hearing how your data is set up if you run through a powerpivot table tutorial you might even rethink your data set-up. The advantage is you don't need to learn vba just learn to apply your current and new excel skills. A good starting point is here:
https://msdn.microsoft.com/en-us/library/gg413497(v=sql.110).aspx
There are also 5 min youtube clips that'll give you a good idea of what else you can do with it.
[Ms SQL]
I've got some data dense sql queries that I view the results of through the SSMS u/i in the datagrid.
The queries are saved as stored procedures that select multiple result sets.
I would like to be able to control the grid formatting a bit more (eg override column widths, decimal formats, right justify numbers, etc).
Is there an alternative to SSMS that would give me more control of the data presentation? It needs to be dynamic and not require a bunch of coding to display a new query (lots of sql work is ad hoc data exploration).
You can set up a data source in an Excel workbook, as long as the dataset isn't too huge.
https://blogs.office.com/2010/06/07/running-a-sql-stored-procedure-from-excel-no-vba/
You could also use SSRS, but Excel would be the fastest way to get going. SSRS is a little more work and probably not what you're looking for.
Edit - you said it returns multiple datasets. I'm not sure that Excel can handle that properly.
I suppose it depends entirely on what you're already comfortable with. Winforms + DataGridView controls inside TabControl objects are really easy to set up. Mostly you just bind the data to the DataGridView controls and they do the right thing based in data types. DataGridView has a virtual mode if your data is real freaking big (gives you control over paging, etc)..but this requires actual code. Old, easy and pretty robust if you're on windows UI...which is assumed given you're into the SSMS UI. Minimal C# or VB.Net required.
Why excel? Well excel is what is used to import the player salaries.
Now I need the spreadsheet to do the following.
Create teams within salary cap.
Include/exclude specific player function
Build multiple lineups from a selected list of players within the cap
Can I do all of this with excel? or do I need to know excel vba as well?
Also which parts of excel or if necessary excel vba must I need to know to code such a thing? Also if someone could give me a short summary of the steps needed to hypothetically make such a thing it would be great. Thanks.
I'm posting this as a reply because it is too long for a comment window.
Just because Excel has a grid doesn't mean that it is fit for data storage and data handling, on the contrary.
What you typically want to do is create a transparent structure that guarantees the integrity of your data and that allows dynamic portability when needed one day.
Excel is meant to be a spreadsheet, people forget this all the time or they just avoid the topic: although Excel has a grid, doesn't mean that it is a good fit for reliable data storage. It is not even the least complex way of storing data, depending on the amount of VBA that you need to manage all these data and the gates that you unnecessarily open towards potential bugs.
This is why an RDBMS is what will fit your needs, in this case Access would be a good option as it preserves your data integrity if you get the table structure right and it executes a lot of tasks for you that you should otherwise need to program yourself to protect the integrity of your data.
Although you can perform SQL on spreadsheets too, note that Excel does NOT cover related tables (what you typically seem to need for building your teams and salary limits), so what many Excel programmers will typically do is to create their own code to make this cross-table data storage thing work.
Don't do this if the alternative is available and much more reliable and future-proof.
At first sight, it seems that you won't even need any VBA; I'm not sure of all the things you want to do, but my first impression is that you can manage everything with SQL syntax and stored queries in MS Access. You can import Excel sheets into Access if you get their format right so that should not be a problem.
Once your data is stored there, rest assured that you have made your life a lot easier.
Looking for some advice in displaying reports with Google charts (for now table reports, but will go on to other types later)
Are people creating a view for each specific report? Or is it better to re-use an existing view and dynamically create the table from it.
I've found some resources where the table columns are dynamically generated, but I am not quite sure how to check and specify the column to be a string or numeric data type.
If I create views for each report, I know ahead of time what the table structure will be and thus making it easier to create, but perhaps more of a nightmare to maintain down the road.
Any thoughts?
Depending on how often the columns/tables change, one of these will work for you.
Create 10 Views
If your data doesn't change too often, just create 10 different DataViews based on the 10 tables you want to create. Since they all use the same underlying data, any change to the original DataTable will automatically be reflected in all 10 tables, and the performance will be much quicker than creating 10 different tables.
If you change the views often, maintenance may be a hassle, so I would suggest a different approach.
Create a DataView Creation Function
You can create a function that will take an array of columns and create a DataView from those columns. This way you can change the views easily by changing the function call only, and will make your code look simpler. Depending on how you want to set the DataView (whether you use filtered rows and/or columns) the function will be slightly different, but this will allow you the most flexibility to change things while giving all the benefits of having 10 dataviews (updating based on changes to the datatable, etc.).
Automate the Whole Kit and Caboose
If you're going to go that far, you can just automate the entire process. Select the rows/columns you want from the DataTable, give a <div> name (or create a <div> automatically), then create the view and the new table chart drawing function. This will work great if your tables all behave the same (have the same events, options, etc.) as it is going to be of use far in to the future.
On the other side, it is more work than the above two to initially create.
I've got a wxGrid that I populate dynamically. I'd like to store some information with each row that shouldn't be displayed to the user. What is the best way to associate data with a row? Should I just create a hidden column or is there a better way?
Creating a hidden column is the fastest, but indeed a very ugly method. If you can justify the effort, then you should better create your own grid table base class. Your own wxGridTableBase-derived class can hold any information you need it to, without the need to show it in the grid. Unfortunately the documentation for that class is sparse or nearly non-existent.
For an example see the grid demo in the wxWidgets samples directory, specifically the BugsGridTable class. What you will notice is that you do not necessarily store the strings that the grid will display, but you can format your data in the GetValue() method. This can be a lot better, both in terms of memory consumption, and because you can change the format of displayed data on-the-fly.
The switch to a custom grid table base class has had a big impact on speed, memory consumption and functionality for the result set data grid of FlameRobin, an administration tool for the Firebird relational database. You can always check out its source code for how we use wxGrid.
Store the value in the row label using SetRowLabelValue and hide the row labels.