Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Set Database Location not showing new fields

Status
Not open for further replies.

Catadmin

Programmer
Oct 26, 2001
3,097
US
Help, please.

I have a location database on my machine (SQL Server 2005) which uses a stored procedure for my dataset. I have a remote database connection (SQL 2000) which has the same exact stored procedure. I go to "Set Database Location" to change which server I'm using. I create the new Connection properly, highlight both stored procedures (they're both the same), and click update.

When it gets to the field mapping screen, the old connection has all the fields listed, but the new connection does not. And when I take my report to the client's location (where my local DB doesn't exist), the same thing happens.

If I click okay, I lose all the fields in the report. ACK!

Does anyone have any thoughts as to how I can change the Server name for my reports without losing my fields or to get the fields on the new connection to show up in the Set Database Location mapping screen?

Thanks in advance.


Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
Verify the database. I do not know the version of Crystal you are using so I cannot tell you exactly how to do this.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"What version of URGENT!!! are you using?
 
I think I figured out. It was a three fold problem. First, I was looking at the wrong stored procedure. @=) WHOOPS!

Secondly, I had an IF/ELSE statement in the stored proc where the field count in the IF part of the statement had 2 more fields than the field count in the ELSE part.

Thirdly, the test database I was pulling against got updated with different data then the data I was testing my report against. So when I entered a table-saved "username" to test my report today, the user didn't exist, so nothing came back for the report because I was entering bad data.

Anyway, I seem to have gotten it to work now. Thanks!



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top