Norman,
Sorry if this is a repeat of something you've already been told. I
didn't have time to read every response but I will take the time to let
you know what we did because it may save you and others a lot of time
in the future..
Using a specific server name will give you grief down the road in the
following areas and there may be more that I haven't considered.
-- UNC paths in default.mfgsys will become obsolete when you move the
backend.
-- links to custom crytstal reports that you attach to the menu will be
wrong.
-- Connection strings and/or ODBC DSNs in your custom Crystal reports
will be wrong.
These things can be avoided by creating a DNS alias using a CNAME
entry. We called ours simply ERP and ERPDB. We added the second alias
called ERPDB anticipating that we'll enventually split the application
and database servers when 10Gb ethernet is commonly available and
affordable.
In our default.mfgsys files, we reference the app server thusly:
<AppServerURL value="AppServerDC://ERP:3091" />
<deploymentServer uri="\\ERP\epicor\mfgsys80" />
Custom report links look like this:
\\erp\epicor\mfgsys80\server\reports\reportname.rpt
Crystal connection strings look like this:
Driver={SQL
Server};Server=ERPDB;Database=mfgsys80;Trusted_Connection=yes;"
One thing to note, you may have to make a registry change to use the
alias as a Windows share. The following article explains how to do it:
http://support.microsoft.com/kb/281308/
By using the alias, you can change out your servers with no impact to
your clients or custom menu items and write reports that can be
deployed to multiple locations without modification.
Brad
Sorry if this is a repeat of something you've already been told. I
didn't have time to read every response but I will take the time to let
you know what we did because it may save you and others a lot of time
in the future..
Using a specific server name will give you grief down the road in the
following areas and there may be more that I haven't considered.
-- UNC paths in default.mfgsys will become obsolete when you move the
backend.
-- links to custom crytstal reports that you attach to the menu will be
wrong.
-- Connection strings and/or ODBC DSNs in your custom Crystal reports
will be wrong.
These things can be avoided by creating a DNS alias using a CNAME
entry. We called ours simply ERP and ERPDB. We added the second alias
called ERPDB anticipating that we'll enventually split the application
and database servers when 10Gb ethernet is commonly available and
affordable.
In our default.mfgsys files, we reference the app server thusly:
<AppServerURL value="AppServerDC://ERP:3091" />
<deploymentServer uri="\\ERP\epicor\mfgsys80" />
Custom report links look like this:
\\erp\epicor\mfgsys80\server\reports\reportname.rpt
Crystal connection strings look like this:
Driver={SQL
Server};Server=ERPDB;Database=mfgsys80;Trusted_Connection=yes;"
One thing to note, you may have to make a registry change to use the
alias as a Windows share. The following article explains how to do it:
http://support.microsoft.com/kb/281308/
By using the alias, you can change out your servers with no impact to
your clients or custom menu items and write reports that can be
deployed to multiple locations without modification.
Brad
--- In vantage@yahoogroups.com, "Norman Hutchins" <nhutchins@...> wrote:
>
> So now that someone has deciphered my question (thank you!) and
> one could any thoughts?
>
>
>
> Thanks,
>
>
>
> Norman
>
>
>
> _____