I have a piece of code (below) that checks a data table (45,000 rows) to see if the row matches any entries in a range elsewhere on the workbook (using custom functions). The routine then creates an array of Flags and writes that array back to a field in the table - so a series of Sumifs formula...
Oddly, I can connect to <server> in SSMS. I can then get to the database in question, look at table layouts, etc., but I don't actually see data. I cannot connect to <server>,<port> in SSMS.
I can connect to <server>,<port> in VS's SQL Server Object Explorer, but I cannot see the table layout there.
> One drawback to PDW is that it does not use SQL Server Management Studio, but uses a third-party tool (this third-party tool is needed because SSMS hasn’t been reworked to connect directly to the control node of the Parallel Data Warehouse). It also uses its own query engine and not all features of SQL Server are supported. And you wouldn’t want to build a solution against SQL Server and then just hope to upsize it to Parallel Data Warehouse Edition.
That's why I can't connect via SSMS...
Apparently, there's no way to they won't allow links from non-Parallel Data Warehouse Edition servers to the vaunted DW, so it looks like it's going to be "extract data, import to my own server" if I want to incorporate any of this data with anything else I've collected...
if they let you run your own SSEE, that might be a better option
I've worked on some departmental projects where they had to do just that because they can't do X on their main Oracle database so we install SQL Server, extract data then massage it to the department's needs.
ah... Well, we do have our own SQL Server (plain Jane, I can connect w/SSMS thank-you-very-much) edition. From what I understand from the guys down the hall, they won't allow any sort of server linking to their precious server
Looks like the only way to query one SQL server from another is to predeclare a Linked Server relationship between them. Since it seems that the overlords who manage the DW have deemed this to be an unnecessary feature to enable. I'm really stuck with select, export to CSV, import.
@McVik again, that is not possible. Most likely you have On Error Resume Next somewhere just swallowing the error, and the condition is systematically entered, and that is a bug. Comment is an object without a default member, your other procedure has a bug. Whether Text is a property or a method makes no difference. Avoid implicit default member calls, your code will be much more reliable as a whole. — Mathieu Guindon3 mins ago
Go. Spend some money and make some memories with your daughter. You'll never remember the cash, but you'll remember the laughs, the smiles and the good times.
Quit trying to be a nerd when you're supposed to be a dad!
@MathieuGuindon - Rubberduck sounds great. I write a lot of VBA procedures especially in MS Excel to help myself to do automatically many boring and recurrent manual things but I have never heard about this project. Thank you for this hint, I'll try it soon. — McVik2 mins ago
@Cyril you can only link to one post but you can mention additional by @<name>ing. The :<numer> is actually a link, rather than a mention, which changes into @<name> once posted.
> **Rubberduck version information** ``` Version 2.4.1.5196 OS: Microsoft Windows NT 10.0.17763.0, x64 Host Product: Microsoft Office 2016 x64 Host Version: 16.0.4912.1000 Host Executable: EXCEL.EXE ```
**Description** RD inspection flags "Set assignment with incompatible object type" error when setting an Excel.Worksheet variable with an Excel.Worksheet codename. This wasn't always flagged by RD in the past though I'm not sure when it started.
> This is a long-standing resolver issue that I wish we could fix before releasing 2.5.0, now that we have what it takes to fix it (namely, identifying the base class for document modules, via the TypeLib API).
Until then, RD doesn't know that `Sheet1` is a `Worksheet`, or that `ThisWorkbook` is a `Workbook`.
I think we should actually reactivate the COM projects load from the API as the second thing after release.
Then. it will get the maximum amount of test time in a prerelease.
The first thing obviously is the SDK change.
Having the API working, will not only give us the supertypes of documents and controls; it also allows to finally implement a 3rd party project exclusion system.
VBA Rubberducking
VBA Rubberducking