Yeah, I did. I put it in my project and guess what, it worked like a champ. I decided to change the BG and FG colors depending on the result. Red BG with White FG if failed, and Green BG with Black FG if success. It works perfectly.
I can't help myself, if I can, I'm going to give another...
Hi gang,
I'm a little stuck. First off let me say that I have absolutely no idea what I'm doing in VB.Net (ok, I know a little, a VERY little).
I'm trying to do a call to a Sub that does a System.Net.DNS.GetHostEntry to return a PTR record of a passed in IP address. I have it working so far...
Thanks for the response John, That's the step I'm on. I have the whitepaper, but haven't had a chance to read it yet. FYI, by "remote", I mean across the internet remote. No VPN.
Thanks again for your advise.
Just a quick question, I installed CRM on a different box than SQL and Reporting Services. I entered the url of the reportserver using the computer name in the address (i.e. http://server1/reportserver) and everything works fine while on the server, however when I Open CRM from a remote PC not...
I have just installed CRM in a 2-server config (CRM on a DC and the SQL server on a non-DC). When trying to connect to CRM using the only configured account, administrator, I am receiving a 403 error in the browser. Has anyone experienced this and if so, can you point in a direction to look in...
Has anyone done a data extraction from a Paradox database in SSIS? In DTS, there was a Paradox connector, but in SSIS, all I can find is the ODBC connection using a DSN that is set to Paradox and thus far, it hasn't worked.
Here's what I've done so far:
1.) Copy the Paradox .db files over to...
I'm in the same boat and test this Friday. Here's my two-cents worth:
Remember that if if you choose A, both DC's in the root domain are GC's thus nulling out the recomendation about not using CG's on FSMO IM servers (From KB Article 223346),
The debate we're actually having is if the answer...
My last post made me think "Duh, why not write the report in Crystal and copy the query?" I did and this is what I found. In order to get the Timestamp format to match in Reporting Services, it has to be structured as such:
SELECT *
FROM dApplicationStat
WHERE Timestamp={ts '2005-12-14...
Thanks for your response Pascal. I tried your example against dApplicationStat in Access and it worked fine. I then copied it over to Reporting services and chnaged it slightly to conform with TSQL syntax. Here's what my query looks like:
SELECT *
FROM dbo.dApplicationStat
WHERE timestamp =...
I've tried YYYY/MM/DD 00:00:00:00, and just the YYYY/MM/DD by itself. Both result in a "Could not parse query" error.
If I change the format to a MS SQL datetime format, i.e. YYYY-MM-DD, I get an error that TIMESTAMP is not not a valid column, however doing a SELECT * clearly show the column...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.