ODBC password for Standard reports with subreports(6.1)

Does it it work fine if the user supply the proper psw ?
If so, then the solution should be in the Windows Registry.

--- In vantage@yahoogroups.com, "kfmonico" <kfmonico@...> wrote:
>
> I have an issue with version 6.1, Crystal 8.5. I modified several
of
> the standard reports, such as quoting, to bring in data from the
system
> using ODBC. I used subreports and never had a problem getting this
to
> work properly. Now, however, we are transfering to new servers
using a
> Citrix like system (2X). I can load the reports in Crystal, tell
it
> where the ODBC files and dbf files are located, verify the
database,
> and can view the reports. However, the system always asks for the
ODBC
> password. When I try and view the reports from Vantage, the system
> will not ask for the ODBC password and when it trys to load the
report
> I get a 599 error. My current system never asked for the ODBC
password
> and works fine. Going back to the new system, if I remove the
> subreport, the report works without any issues, so I am sure it is
a
> problem with the ODBC subreports. Is there someway to set up the
ODBC
> driver to ask for the password? Or, better yet to work the way it
> works now on my old system to work without a password? I would
> appreciate any help if someone ran into this before.
>
I have an issue with version 6.1, Crystal 8.5. I modified several of
the standard reports, such as quoting, to bring in data from the system
using ODBC. I used subreports and never had a problem getting this to
work properly. Now, however, we are transfering to new servers using a
Citrix like system (2X). I can load the reports in Crystal, tell it
where the ODBC files and dbf files are located, verify the database,
and can view the reports. However, the system always asks for the ODBC
password. When I try and view the reports from Vantage, the system
will not ask for the ODBC password and when it trys to load the report
I get a 599 error. My current system never asked for the ODBC password
and works fine. Going back to the new system, if I remove the
subreport, the report works without any issues, so I am sure it is a
problem with the ODBC subreports. Is there someway to set up the ODBC
driver to ask for the password? Or, better yet to work the way it
works now on my old system to work without a password? I would
appreciate any help if someone ran into this before.
 I know that we have to have the 'Vantage Launch Scipts' configured pointing to the ODBC driver ( the script behinf the launch icons), ie:
Â
[MFG Startup]
Executable=V:\prgs91d\bin\prowin32.exe
Database=V:\mfgsys61\db\MFGSYS
IniFile=V:\mfgsys61\mfgsys.ini
ParameterFile=V:\mfgsys61\db\mfgsys.pf
ConnectOptions=-N TCP -H eevantage -S 6100 -ld MFGSYS
TempDirectory=C:\Epicor\MfgWrk61
StartupProcedure=mainmenu.w
OtherParameters=-rand 2 -q -basekey ini
mfgsys=VN
mfglanguage=enu
mfgtranslator=yes
unicode=true
MFGODBCpasswd=odbcuser
MFGODBCUser=odbcuser
MFGODBCDbse=mfgsys
MFGODBCServer=eeVantage_Mfg

--- On Wed, 8/20/08, kfmonico <kfmonico@...> wrote:

From: kfmonico <kfmonico@...>
Subject: [Vantage] ODBC password for Standard reports with subreports(6.1)
To: vantage@yahoogroups.com
Date: Wednesday, August 20, 2008, 12:09 PM






I have an issue with version 6.1, Crystal 8.5. I modified several of
the standard reports, such as quoting, to bring in data from the system
using ODBC. I used subreports and never had a problem getting this to
work properly. Now, however, we are transfering to new servers using a
Citrix like system (2X). I can load the reports in Crystal, tell it
where the ODBC files and dbf files are located, verify the database,
and can view the reports. However, the system always asks for the ODBC
password. When I try and view the reports from Vantage, the system
will not ask for the ODBC password and when it trys to load the report
I get a 599 error. My current system never asked for the ODBC password
and works fine. Going back to the new system, if I remove the
subreport, the report works without any issues, so I am sure it is a
problem with the ODBC subreports. Is there someway to set up the ODBC
driver to ask for the password? Or, better yet to work the way it
works now on my old system to work without a password? I would
appreciate any help if someone ran into this before.


















[Non-text portions of this message have been removed]
Good Afternoon everyone,



Does anyone have a bpm that checks whenever a user clicks on the counter sale button on the order entry screen? I would like to modify it to fill in our address. If that is not possible does anyone have a different way to do it?



Thanks!





Dale Kalsow | Information Technologies Director
____________________________________________________________________
Determan Brownie, Inc. | 1241 72nd Avenue NE | Minneapolis, MN 55432

( Phone: (763) 502-9689 | ( Fax: (763) 571-1789

* dale.r.kalsow@... | ý http://determan.com/



"Ambition is the path to success. Persistence is the vehicle you arrive in."



Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation.







[Non-text portions of this message have been removed]
Have you modified the 6.1 vantage file to include the ODBC DSN
information?



Gary





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of kfmonico
Sent: 20 August 2008 17:09
To: vantage@yahoogroups.com
Subject: [Vantage] ODBC password for Standard reports with
subreports(6.1)



I have an issue with version 6.1, Crystal 8.5. I modified several of
the standard reports, such as quoting, to bring in data from the system
using ODBC. I used subreports and never had a problem getting this to
work properly. Now, however, we are transfering to new servers using a
Citrix like system (2X). I can load the reports in Crystal, tell it
where the ODBC files and dbf files are located, verify the database,
and can view the reports. However, the system always asks for the ODBC
password. When I try and view the reports from Vantage, the system
will not ask for the ODBC password and when it trys to load the report
I get a 599 error. My current system never asked for the ODBC password
and works fine. Going back to the new system, if I remove the
subreport, the report works without any issues, so I am sure it is a
problem with the ODBC subreports. Is there someway to set up the ODBC
driver to ask for the password? Or, better yet to work the way it
works now on my old system to work without a password? I would
appreciate any help if someone ran into this before.





[Non-text portions of this message have been removed]
I'm on Vantage 8 and Crystal 11, so this may or may not help, but what I did to solve this problem was embed the password in the ODBC connection string.
E.g.: "Driver ={SQL Server};Server=server;Database=mfgsys803;uid=username;Pwd=password;"

I'm on Crystal 11, I don't know if it works with your version, but give it a try.

When you choose the ODBC data source, you pick the from the DSNs set up on your system, or a File DSN, or a Connection String. Enter the string I put, but changing it to your server, password and so on.
Weird thing is, even though you have entered server, user and password as part of the connection string, you'll still be prompted for it in Crystal. Don't worry, end user will not be prompted though.
Hope this helps with your versions.

TOny




From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of kfmonico
Sent: 20 August 2008 17:09
To: vantage@yahoogroups .com
Subject: [Vantage] ODBC password for Standard reports with
subreports(6. 1)

I have an issue with version 6.1, Crystal 8.5. I modified several of
the standard reports, such as quoting, to bring in data from the system
using ODBC. I used subreports and never had a problem getting this to
work properly. Now, however, we are transfering to new servers using a
Citrix like system (2X). I can load the reports in Crystal, tell it
where the ODBC files and dbf files are located, verify the database,
and can view the reports. However, the system always asks for the ODBC
password. When I try and view the reports from Vantage, the system
will not ask for the ODBC password and when it trys to load the report
I get a 599 error. My current system never asked for the ODBC password
and works fine. Going back to the new system, if I remove the
subreport, the report works without any issues, so I am sure it is a
problem with the ODBC subreports. Is there someway to set up the ODBC
driver to ask for the password? Or, better yet to work the way it
works now on my old system to work without a password? I would
appreciate any help if someone ran into this before.

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]
> I'm on Vantage 8 and Crystal 11, so this may or may not help, but what I
> did to solve this problem was embed the password in the ODBC connection
> string.
> E.g.: "Driver ={SQL
> Server};Server=server;Database=mfgsys803;uid=username;Pwd=password;"

As an aside, you can set up SQL Server to use Windows Authentication (a
trusted connection) and it will use a Windows Security Group to allow access
to the database. In this case, there wouldn't be any password prompting.

I prefer this method because if an employee leaves, their disabled account
won't have access. But if you use SQL Security (username and password), you
have to change the password and then go and find everywhere it's embedded
and change them there as well. Quite a PITA.

Mark W.
I was not able to get the embedded ODBC string to work unless the SQL Security account and password were same as the ODBC account and password, as defined in System Agent.
Even if say, user account sqluser with password *pass#$ exists on the SQL Server, and I embed that info in a connection string, it would not work unless that was what was defined in System Agent.
Only when I create the SQL account that precisely matches the account and password in System Agent, could I get the subreports to work.
However, our users are on thin clients using Citrix, and this might have everything to do with it.







----- Original Message ----
From: Mark Wonsil <mark_wonsil@...>
To: vantage@yahoogroups.com
Sent: Thursday, August 21, 2008 10:53:36 AM
Subject: RE: [Vantage] ODBC password for Standard reports with subreports(6.1)


> I'm on Vantage 8 and Crystal 11, so this may or may not help, but what I
> did to solve this problem was embed the password in the ODBC connection
> string.
> E.g.: "Driver ={SQL
> Server};Server= server;Database= mfgsys803; uid=username; Pwd=password; "

As an aside, you can set up SQL Server to use Windows Authentication (a
trusted connection) and it will use a Windows Security Group to allow access
to the database. In this case, there wouldn't be any password prompting.

I prefer this method because if an employee leaves, their disabled account
won't have access. But if you use SQL Security (username and password), you
have to change the password and then go and find everywhere it's embedded
and change them there as well. Quite a PITA.

Mark W.






[Non-text portions of this message have been removed]