I am trying to access tables in SPSS Version 24 but can't find it. Usually it should be on Analyze -> Tables, but I don't have Tables under Analyze.
Thank you
In a syntax window, issue this command:
SHOW LICENSE.
In the Output Viewer a table will appear showing you what you are licensed for.
Related
I have been evaluating Rubymine recently which is an amazing IDE, probably the most complete for Rails. Though I think I prefer the ergonomy of SublimeText and all its customizable packages.
Though I really miss one feature: the database tab on the right that gives me an up-to-date overview of my database structure and records.
I can't find a similar package for SublimeText and was wondering if it existed at all ?
I just want to have the results from a simple select statement exported to excel. It seems like the only options now are grid or text. In previous versions this was obvious from the menu but now I can't find it at all! Am I missing something??
A direct export to Excel isn't (and never has been) offered by Pervasive. You can export to CSV / SDF and open that file in Excel.
In PSQL v11, you can export the data by right clicking the table name in PCC and selecting "Export Data".
If you want to export more than one table at a time or on a scheduled basis, you need a different tool.
I can't seem to find much documentation for the code that Power Tools Beta 4 generates. I'm particularly interested in how to modify the code when new table fields are added, and how to add relationships. Where can I find a description of all the code pieces that are generated?
Also, I thought there was a way to regenerate and overwrite the Power Tools code after it has been generated but I just get errors when I try to do that. Do I need to delete all the generated entities in order to re-generate?
I am working with an undocumented, 100.000 lines Delphi 7 project and one of my goals is to create a software architecture document from the source code.
Can you give me any ideas on how to approach this?
These tools work with Delphi 7 and are of great help:
the UML tool ModelMaker
the refacotoring tool ModelMaker Code Explorer
the documentation tool Documentation Insight (as of august 2012)
UML diagrams are a great way to get an overview of structure. How well that overview is, depends on how well the structure is.
For taking over projects like these, I start with some basic documentation (often in MarkDown format, as that text based format is version control friendly, and generates nice HTML).
To get that going, it helps if the original developers or/and some base documentation are still there.
Then just start to:
fix bugs / apply feature requests
use ModelMaker to get a feel for overall structure
use ModelMaker Code Explorer as a refactoring tool
use Documentation Insight to document inside the source code (you can generate help files and web pages with the pro version, see feature matrix)
update my Markdown documents with any information that does not fit in the source code documentation well
Note you can put some documentation in using Model Maker Code Explorer, but it can not be exported as help files, since it uses a different documentation format than Documentation Insight.
So I agree with the comment by Jan Doggen (thanks Jan!): just start. Make sure you have the right tools to help that going.
Try running the source code through a newer Delphi version that supports UML modeling, then let it show you how different sections of code related to each other.
Understand will do the job. Free download includes 15 days evaluation which will be more then enough for what you need to document.
For example, if I profile:
C:\Program Files\Application Build 1\MyApp.exe
C:\Program Files\Application Build 2\MyApp.exe
And I then import both sets of results into a single AQTime project and attempt to compare them, AQTime doesn't match up any of the corresponding functions in each. I'm assuming that while it's comparing, when it comes across two functions with the same name but different module name, it's concluding that they're not the same function and then putting them in separate rows in the output table. How can it be made to ignore the module name?
As far as I can see, the module names are the same - the difference is in the path. Try disabling the "File names with path" option on the Profiler toolbar (it is shown at the top of the Report panel).
If this does not give the expected results, post here a screenshot demonstrating your situation.
Best regards,
Alex
AutomatedQA Support Team