can also use this freeware tool as well DBComparer[/url]

you will need trusts in place between the domains, kerberos authentication and SPN's setting up to allow the pass through of windows authentication accounts to cross domains

all forum topics stay active, they cant be closed

glad you got it working

for the benefit of others could you detail the problem and resolution incase someone else has the same...

you will need to add in the image of the person and the image of the uni logo as images to the report

create a rectangle which has a background image...

1 - image is a depreciated data type, use nvarchar(max), varchar(max), varbinary(max) instead

2 - filestream might be a better option and saves on the DB as it send the file...

sorry that is unclear to me I do appologise

do you have the images you want to use? can you attach them and I can put them in a report...

what is your expression with the change to ytd2011 and what value fro ytd2012 is being used 0 still?

Lowell (3/28/2012)

---

here's one way to do it;

the typical chars you are looking for are highascii between 160 and 255;

here i'm just using a row_number() function generate a table of numbers...

firstly that query looks incorrect as your only ever going to be looking at the last character in the string being a special character not the whole string

SELECT Description, FROM...

do you want the background image to be completly in the background which covers the whole of the report page? and I take it the corner image is the company...

other than management studio. im not sure.

as your dividing by ytd2011 thats the one you need to check is 0, not ytd2012, missed that at first look

=IIF((Fields!TG___2012_YTD.Value) = 0,0,

((Fields!TG___2012_YTD.Value) - (Fields!TG___2011_YTD.Value)/Fields!TG___2011_YTD.Value) *100)

the problem on the above is the second 0 as your still passing in 0 to divide by, change it to 1 so that...

you can go into the login at the server level in the security/logins folder to see what server level securables the login has, then at the DB level in security/users...

another way to do it

CREATE TABLE [dbo].[tab1](

[NUM] [int] NULL,

[bdDQLinkID] [nvarchar](255) NULL,

[bdDQID] [nvarchar](255) NULL,

[bdID] [int] NOT NULL,

[bdSalutation] [nvarchar](255) NULL,

[bdFirstName] [nvarchar](255) NULL,

[bdMiddleName] [nvarchar](255) NULL,

[bdSurname] [nvarchar](255) NULL,

[bdFullName] [nvarchar](255) NULL,

[bdTitle] [nvarchar](255) NULL,

[bdPhoneNumber] [nvarchar](255) NULL,

[bdEmail]...