"B. Horstmanshof" wrote:

> I have a sql2000 server that I am contemplating downgrading to sql7....
>
> The scenario is this:
> The server was originally NT4, upgraded to Server2000.
> The server ran Accountmate using SQL7.
> SQL was upgraded to 2000.
>
> Turns out that the SQL2000 is not entirely compatible with the Accountmate -
> I don't have the exact reasons why.  The application generates an error
> about a login name on startup.  The user clicks ok, then continues without a
> problem.
> The client and Accountmate reps elected to leave as is.  It has been about
> two years now!
>
> With the exception of adding data, no modifications have been made to the
> databases since.
>
> Is it possible to do the downgrade?
> What are the implications of doing?
> Where would I go to get specifics to the procedure?
>
> Thanks in advance for any help.
> Bruce.
>
>
>

"John Bell" <jbellnewspo***@hotmail.com> wrote in message
news:A66A999D-2C70-4995-940A-387F58312CA4@microsoft.com...
> Hi
>
> You are downgrading to a product that will come to the end of it's life
> sooner than the one you are on, which can't be good. I assume you are not
> paying anything for the support of this package? If the login issue is
your
> only problem then I would try to find out why this happens rather than
hoping
> a downgrade will solve it. Do you get anything written into the SQL server
> log or an specific error message/number?
>
> John
>
>
>
> "B. Horstmanshof" wrote:
>
> > I have a sql2000 server that I am contemplating downgrading to sql7....
> >
> > The scenario is this:
> > The server was originally NT4, upgraded to Server2000.
> > The server ran Accountmate using SQL7.
> > SQL was upgraded to 2000.
> >
> > Turns out that the SQL2000 is not entirely compatible with the
Accountmate -
> > I don't have the exact reasons why.  The application generates an error
> > about a login name on startup.  The user clicks ok, then continues
without a
> > problem.
> > The client and Accountmate reps elected to leave as is.  It has been
about
> > two years now!
> >
> > With the exception of adding data, no modifications have been made to
the
> > databases since.
> >
> > Is it possible to do the downgrade?
> > What are the implications of doing?
> > Where would I go to get specifics to the procedure?
> >
> > Thanks in advance for any help.
> > Bruce.
> >
> >
> >

"B. Horstmanshof" wrote:

> Hi John.
>
> We are not paying support for this package.  The pop-up error claims to be a
> connectivity error:
>
> Error # [1526]:  Connectivity error: [Microsoft][ODBC SQL Server Driver][SQL
> Server]Invalid column name 'suid'.
>
> SQL Stmt:
> select name from sysusers where suid in (select suid master..sysusers where
> name='vamlogin') and name='dbo'
>
> They way it was explained to me is (as best I remember) that the name is
> used for something else or can't be used in SQL2000, but must exisit with
> this version of Accountmate.  It was a while ago, and nobody seemed worried
> about it!
>
> Ideally the client would upgrade the software and move to 2003, but it is
> always a money issue - they would need to upgrade servers, o/s, sql and
> application, and they can't see the benefit of spending that kind of money!
>
> The backwards move would be to put the application on the platform it was
> supposed to be on, and see if the performance issues disappear.
>
> Bruce
>
>
> "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> news:A66A999D-2C70-4995-940A-387F58312CA4@microsoft.com...
> > Hi
> >
> > You are downgrading to a product that will come to the end of it's life
> > sooner than the one you are on, which can't be good. I assume you are not
> > paying anything for the support of this package? If the login issue is
> your
> > only problem then I would try to find out why this happens rather than
> hoping
> > a downgrade will solve it. Do you get anything written into the SQL server
> > log or an specific error message/number?
> >
> > John
> >
> >
> >
> > "B. Horstmanshof" wrote:
> >
> > > I have a sql2000 server that I am contemplating downgrading to sql7....
> > >
> > > The scenario is this:
> > > The server was originally NT4, upgraded to Server2000.
> > > The server ran Accountmate using SQL7.
> > > SQL was upgraded to 2000.
> > >
> > > Turns out that the SQL2000 is not entirely compatible with the
> Accountmate -
> > > I don't have the exact reasons why.  The application generates an error
> > > about a login name on startup.  The user clicks ok, then continues
> without a
> > > problem.
> > > The client and Accountmate reps elected to leave as is.  It has been
> about
> > > two years now!
> > >
> > > With the exception of adding data, no modifications have been made to
> the
> > > databases since.
> > >
> > > Is it possible to do the downgrade?
> > > What are the implications of doing?
> > > Where would I go to get specifics to the procedure?
> > >
> > > Thanks in advance for any help.
> > > Bruce.
> > >
> > >
> > >
>
>
>

"John Bell" <jbellnewspo***@hotmail.com> wrote in message
news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@microsoft.com...
> Hi Bruce
>
> As they are querying the system catalogs directly then you can't easily
> overcome this unless it is in a stored procedure where the code can be
> changed. it looks like it is checking the user is in the dbo which could
be
> found by other methods.
>
> If this does not affect the functionality why would you want to revert
back?
>
> John
>
>
> "B. Horstmanshof" wrote:
>
> > Hi John.
> >
> > We are not paying support for this package.  The pop-up error claims to
be a
> > connectivity error:
> >
> > Error # [1526]:  Connectivity error: [Microsoft][ODBC SQL Server
Driver][SQL
> > Server]Invalid column name 'suid'.
> >
> > SQL Stmt:
> > select name from sysusers where suid in (select suid master..sysusers
where
> > name='vamlogin') and name='dbo'
> >
> > They way it was explained to me is (as best I remember) that the name is
> > used for something else or can't be used in SQL2000, but must exisit
with
> > this version of Accountmate.  It was a while ago, and nobody seemed
worried
> > about it!
> >
> > Ideally the client would upgrade the software and move to 2003, but it
is
> > always a money issue - they would need to upgrade servers, o/s, sql and
> > application, and they can't see the benefit of spending that kind of
money!
> >
> > The backwards move would be to put the application on the platform it
was
> > supposed to be on, and see if the performance issues disappear.
> >
> > Bruce
> >
> >
> > "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> > news:A66A999D-2C70-4995-940A-387F58312CA4@microsoft.com...
> > > Hi
> > >
> > > You are downgrading to a product that will come to the end of it's
life
> > > sooner than the one you are on, which can't be good. I assume you are
not
> > > paying anything for the support of this package? If the login issue is
> > your
> > > only problem then I would try to find out why this happens rather than
> > hoping
> > > a downgrade will solve it. Do you get anything written into the SQL
server
> > > log or an specific error message/number?
> > >
> > > John
> > >
> > >
> > >
> > > "B. Horstmanshof" wrote:
> > >
> > > > I have a sql2000 server that I am contemplating downgrading to
sql7....
> > > >
> > > > The scenario is this:
> > > > The server was originally NT4, upgraded to Server2000.
> > > > The server ran Accountmate using SQL7.
> > > > SQL was upgraded to 2000.
> > > >
> > > > Turns out that the SQL2000 is not entirely compatible with the
> > Accountmate -
> > > > I don't have the exact reasons why.  The application generates an
error
> > > > about a login name on startup.  The user clicks ok, then continues
> > without a
> > > > problem.
> > > > The client and Accountmate reps elected to leave as is.  It has been
> > about
> > > > two years now!
> > > >
> > > > With the exception of adding data, no modifications have been made
to
> > the
> > > > databases since.
> > > >
> > > > Is it possible to do the downgrade?
> > > > What are the implications of doing?
> > > > Where would I go to get specifics to the procedure?
> > > >
> > > > Thanks in advance for any help.
> > > > Bruce.
> > > >
> > > >
> > > >
> >
> >
> >

"B. Horstmanshof" wrote:

> The server is having problems - slow and apparently stalling.  I have
> noticed that the cpu usage on the system remain high for minutes at a time.
> There is a second server with the same setup (but using sql7) that is for a
> separate company in the same network.  The databases are similar in size and
> no one is having a problem with that system.
>
> I figure that if I have to rebuild or reinstall things, I should give the
> apps what they want (namely sql7).
>
>
> "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@microsoft.com...
> > Hi Bruce
> >
> > As they are querying the system catalogs directly then you can't easily
> > overcome this unless it is in a stored procedure where the code can be
> > changed. it looks like it is checking the user is in the dbo which could
> be
> > found by other methods.
> >
> > If this does not affect the functionality why would you want to revert
> back?
> >
> > John
> >
> >
> > "B. Horstmanshof" wrote:
> >
> > > Hi John.
> > >
> > > We are not paying support for this package.  The pop-up error claims to
> be a
> > > connectivity error:
> > >
> > > Error # [1526]:  Connectivity error: [Microsoft][ODBC SQL Server
> Driver][SQL
> > > Server]Invalid column name 'suid'.
> > >
> > > SQL Stmt:
> > > select name from sysusers where suid in (select suid master..sysusers
> where
> > > name='vamlogin') and name='dbo'
> > >
> > > They way it was explained to me is (as best I remember) that the name is
> > > used for something else or can't be used in SQL2000, but must exisit
> with
> > > this version of Accountmate.  It was a while ago, and nobody seemed
> worried
> > > about it!
> > >
> > > Ideally the client would upgrade the software and move to 2003, but it
> is
> > > always a money issue - they would need to upgrade servers, o/s, sql and
> > > application, and they can't see the benefit of spending that kind of
> money!
> > >
> > > The backwards move would be to put the application on the platform it
> was
> > > supposed to be on, and see if the performance issues disappear.
> > >
> > > Bruce
> > >
> > >
> > > "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> > > news:A66A999D-2C70-4995-940A-387F58312CA4@microsoft.com...
> > > > Hi
> > > >
> > > > You are downgrading to a product that will come to the end of it's
> life
> > > > sooner than the one you are on, which can't be good. I assume you are
> not
> > > > paying anything for the support of this package? If the login issue is
> > > your
> > > > only problem then I would try to find out why this happens rather than
> > > hoping
> > > > a downgrade will solve it. Do you get anything written into the SQL
> server
> > > > log or an specific error message/number?
> > > >
> > > > John
> > > >
> > > >
> > > >
> > > > "B. Horstmanshof" wrote:
> > > >
> > > > > I have a sql2000 server that I am contemplating downgrading to
> sql7....
> > > > >
> > > > > The scenario is this:
> > > > > The server was originally NT4, upgraded to Server2000.
> > > > > The server ran Accountmate using SQL7.
> > > > > SQL was upgraded to 2000.
> > > > >
> > > > > Turns out that the SQL2000 is not entirely compatible with the
> > > Accountmate -
> > > > > I don't have the exact reasons why.  The application generates an
> error
> > > > > about a login name on startup.  The user clicks ok, then continues
> > > without a
> > > > > problem.
> > > > > The client and Accountmate reps elected to leave as is.  It has been
> > > about
> > > > > two years now!
> > > > >
> > > > > With the exception of adding data, no modifications have been made
> to
> > > the
> > > > > databases since.
> > > > >
> > > > > Is it possible to do the downgrade?
> > > > > What are the implications of doing?
> > > > > Where would I go to get specifics to the procedure?
> > > > >
> > > > > Thanks in advance for any help.
> > > > > Bruce.
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>

"John Bell" <jbellnewspo***@hotmail.com> wrote in message
news:56E40227-C36C-408C-970E-6EDDE317BB66@microsoft.com...
> Hi Bruce,
>
> What sort of maintenance is is undertaken on this database?
>
> John
>
> "B. Horstmanshof" wrote:
>
> > The server is having problems - slow and apparently stalling.  I have
> > noticed that the cpu usage on the system remain high for minutes at a
time.
> > There is a second server with the same setup (but using sql7) that is
for a
> > separate company in the same network.  The databases are similar in size
and
> > no one is having a problem with that system.
> >
> > I figure that if I have to rebuild or reinstall things, I should give
the
> > apps what they want (namely sql7).
> >
> >
> > "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> > news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@microsoft.com...
> > > Hi Bruce
> > >
> > > As they are querying the system catalogs directly then you can't
easily
> > > overcome this unless it is in a stored procedure where the code can be
> > > changed. it looks like it is checking the user is in the dbo which
could
> > be
> > > found by other methods.
> > >
> > > If this does not affect the functionality why would you want to revert
> > back?
> > >
> > > John
> > >
> > >
> > > "B. Horstmanshof" wrote:
> > >
> > > > Hi John.
> > > >
> > > > We are not paying support for this package.  The pop-up error claims
to
> > be a
> > > > connectivity error:
> > > >
> > > > Error # [1526]:  Connectivity error: [Microsoft][ODBC SQL Server
> > Driver][SQL
> > > > Server]Invalid column name 'suid'.
> > > >
> > > > SQL Stmt:
> > > > select name from sysusers where suid in (select suid
master..sysusers
> > where
> > > > name='vamlogin') and name='dbo'
> > > >
> > > > They way it was explained to me is (as best I remember) that the
name is
> > > > used for something else or can't be used in SQL2000, but must exisit
> > with
> > > > this version of Accountmate.  It was a while ago, and nobody seemed
> > worried
> > > > about it!
> > > >
> > > > Ideally the client would upgrade the software and move to 2003, but
it
> > is
> > > > always a money issue - they would need to upgrade servers, o/s, sql
and
> > > > application, and they can't see the benefit of spending that kind of
> > money!
> > > >
> > > > The backwards move would be to put the application on the platform
it
> > was
> > > > supposed to be on, and see if the performance issues disappear.
> > > >
> > > > Bruce
> > > >
> > > >
> > > > "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> > > > news:A66A999D-2C70-4995-940A-387F58312CA4@microsoft.com...
> > > > > Hi
> > > > >
> > > > > You are downgrading to a product that will come to the end of it's
> > life
> > > > > sooner than the one you are on, which can't be good. I assume you
are
> > not
> > > > > paying anything for the support of this package? If the login
issue is
> > > > your
> > > > > only problem then I would try to find out why this happens rather
than
> > > > hoping
> > > > > a downgrade will solve it. Do you get anything written into the
SQL
> > server
> > > > > log or an specific error message/number?
> > > > >
> > > > > John
> > > > >
> > > > >
> > > > >
> > > > > "B. Horstmanshof" wrote:
> > > > >
> > > > > > I have a sql2000 server that I am contemplating downgrading to
> > sql7....
> > > > > >
> > > > > > The scenario is this:
> > > > > > The server was originally NT4, upgraded to Server2000.
> > > > > > The server ran Accountmate using SQL7.
> > > > > > SQL was upgraded to 2000.
> > > > > >
> > > > > > Turns out that the SQL2000 is not entirely compatible with the
> > > > Accountmate -
> > > > > > I don't have the exact reasons why.  The application generates
an
> > error
> > > > > > about a login name on startup.  The user clicks ok, then
continues
> > > > without a
> > > > > > problem.
> > > > > > The client and Accountmate reps elected to leave as is.  It has
been
> > > > about
> > > > > > two years now!
> > > > > >
> > > > > > With the exception of adding data, no modifications have been
made
> > to
> > > > the
> > > > > > databases since.
> > > > > >
> > > > > > Is it possible to do the downgrade?
> > > > > > What are the implications of doing?
> > > > > > Where would I go to get specifics to the procedure?
> > > > > >
> > > > > > Thanks in advance for any help.
> > > > > > Bruce.
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >

"B. Horstmanshof" wrote:

> Just backups (to disk) and optimization (reorganize pages and change free
> space to 10%), both run through the Database maintenance plan on a daily
> schedule.
> The Application vendor takes care of that end - so I hope I answered the
> question correctly!
>
> "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> news:56E40227-C36C-408C-970E-6EDDE317BB66@microsoft.com...
> > Hi Bruce,
> >
> > What sort of maintenance is is undertaken on this database?
> >
> > John
> >
> > "B. Horstmanshof" wrote:
> >
> > > The server is having problems - slow and apparently stalling.  I have
> > > noticed that the cpu usage on the system remain high for minutes at a
> time.
> > > There is a second server with the same setup (but using sql7) that is
> for a
> > > separate company in the same network.  The databases are similar in size
> and
> > > no one is having a problem with that system.
> > >
> > > I figure that if I have to rebuild or reinstall things, I should give
> the
> > > apps what they want (namely sql7).
> > >
> > >
> > > "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> > > news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@microsoft.com...
> > > > Hi Bruce
> > > >
> > > > As they are querying the system catalogs directly then you can't
> easily
> > > > overcome this unless it is in a stored procedure where the code can be
> > > > changed. it looks like it is checking the user is in the dbo which
> could
> > > be
> > > > found by other methods.
> > > >
> > > > If this does not affect the functionality why would you want to revert
> > > back?
> > > >
> > > > John
> > > >
> > > >
> > > > "B. Horstmanshof" wrote:
> > > >
> > > > > Hi John.
> > > > >
> > > > > We are not paying support for this package.  The pop-up error claims
> to
> > > be a
> > > > > connectivity error:
> > > > >
> > > > > Error # [1526]:  Connectivity error: [Microsoft][ODBC SQL Server
> > > Driver][SQL
> > > > > Server]Invalid column name 'suid'.
> > > > >
> > > > > SQL Stmt:
> > > > > select name from sysusers where suid in (select suid
> master..sysusers
> > > where
> > > > > name='vamlogin') and name='dbo'
> > > > >
> > > > > They way it was explained to me is (as best I remember) that the
> name is
> > > > > used for something else or can't be used in SQL2000, but must exisit
> > > with
> > > > > this version of Accountmate.  It was a while ago, and nobody seemed
> > > worried
> > > > > about it!
> > > > >
> > > > > Ideally the client would upgrade the software and move to 2003, but
> it
> > > is
> > > > > always a money issue - they would need to upgrade servers, o/s, sql
> and
> > > > > application, and they can't see the benefit of spending that kind of
> > > money!
> > > > >
> > > > > The backwards move would be to put the application on the platform
> it
> > > was
> > > > > supposed to be on, and see if the performance issues disappear.
> > > > >
> > > > > Bruce
> > > > >
> > > > >
> > > > > "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> > > > > news:A66A999D-2C70-4995-940A-387F58312CA4@microsoft.com...
> > > > > > Hi
> > > > > >
> > > > > > You are downgrading to a product that will come to the end of it's
> > > life
> > > > > > sooner than the one you are on, which can't be good. I assume you
> are
> > > not
> > > > > > paying anything for the support of this package? If the login
> issue is
> > > > > your
> > > > > > only problem then I would try to find out why this happens rather
> than
> > > > > hoping
> > > > > > a downgrade will solve it. Do you get anything written into the
> SQL
> > > server
> > > > > > log or an specific error message/number?
> > > > > >
> > > > > > John
> > > > > >
> > > > > >
> > > > > >
> > > > > > "B. Horstmanshof" wrote:
> > > > > >
> > > > > > > I have a sql2000 server that I am contemplating downgrading to
> > > sql7....
> > > > > > >
> > > > > > > The scenario is this:
> > > > > > > The server was originally NT4, upgraded to Server2000.
> > > > > > > The server ran Accountmate using SQL7.
> > > > > > > SQL was upgraded to 2000.
> > > > > > >
> > > > > > > Turns out that the SQL2000 is not entirely compatible with the
> > > > > Accountmate -
> > > > > > > I don't have the exact reasons why.  The application generates
> an
> > > error
> > > > > > > about a login name on startup.  The user clicks ok, then
> continues
> > > > > without a
> > > > > > > problem.
> > > > > > > The client and Accountmate reps elected to leave as is.  It has
> been
> > > > > about
> > > > > > > two years now!
> > > > > > >
> > > > > > > With the exception of adding data, no modifications have been
> made
> > > to
> > > > > the
> > > > > > > databases since.
> > > > > > >
> > > > > > > Is it possible to do the downgrade?
> > > > > > > What are the implications of doing?
> > > > > > > Where would I go to get specifics to the procedure?
> > > > > > >
> > > > > > > Thanks in advance for any help.
> > > > > > > Bruce.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>

"John Bell" <jbellnewspo***@hotmail.com> wrote in message
news:29CB601C-C569-4625-8E82-9C68CE01EEE1@microsoft.com...
> Hi
>
> If the jobs have not been failing then it sounds like it should be ok,
have
> you tried profiler to identify slow queries and missing
indexes/statistics?
>
> John
>
> "B. Horstmanshof" wrote:
>
> > Just backups (to disk) and optimization (reorganize pages and change
free
> > space to 10%), both run through the Database maintenance plan on a daily
> > schedule.
> > The Application vendor takes care of that end - so I hope I answered the
> > question correctly!
> >
> > "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> > news:56E40227-C36C-408C-970E-6EDDE317BB66@microsoft.com...
> > > Hi Bruce,
> > >
> > > What sort of maintenance is is undertaken on this database?
> > >
> > > John
> > >
> > > "B. Horstmanshof" wrote:
> > >
> > > > The server is having problems - slow and apparently stalling.  I
have
> > > > noticed that the cpu usage on the system remain high for minutes at
a
> > time.
> > > > There is a second server with the same setup (but using sql7) that
is
> > for a
> > > > separate company in the same network.  The databases are similar in
size
> > and
> > > > no one is having a problem with that system.
> > > >
> > > > I figure that if I have to rebuild or reinstall things, I should
give
> > the
> > > > apps what they want (namely sql7).
> > > >
> > > >
> > > > "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> > > > news:A1B28A17-7343-4569-B8AF-0E2FE8D9E3C4@microsoft.com...
> > > > > Hi Bruce
> > > > >
> > > > > As they are querying the system catalogs directly then you can't
> > easily
> > > > > overcome this unless it is in a stored procedure where the code
can be
> > > > > changed. it looks like it is checking the user is in the dbo which
> > could
> > > > be
> > > > > found by other methods.
> > > > >
> > > > > If this does not affect the functionality why would you want to
revert
> > > > back?
> > > > >
> > > > > John
> > > > >
> > > > >
> > > > > "B. Horstmanshof" wrote:
> > > > >
> > > > > > Hi John.
> > > > > >
> > > > > > We are not paying support for this package.  The pop-up error
claims
> > to
> > > > be a
> > > > > > connectivity error:
> > > > > >
> > > > > > Error # [1526]:  Connectivity error: [Microsoft][ODBC SQL Server
> > > > Driver][SQL
> > > > > > Server]Invalid column name 'suid'.
> > > > > >
> > > > > > SQL Stmt:
> > > > > > select name from sysusers where suid in (select suid
> > master..sysusers
> > > > where
> > > > > > name='vamlogin') and name='dbo'
> > > > > >
> > > > > > They way it was explained to me is (as best I remember) that the
> > name is
> > > > > > used for something else or can't be used in SQL2000, but must
exisit
> > > > with
> > > > > > this version of Accountmate.  It was a while ago, and nobody
seemed
> > > > worried
> > > > > > about it!
> > > > > >
> > > > > > Ideally the client would upgrade the software and move to 2003,
but
> > it
> > > > is
> > > > > > always a money issue - they would need to upgrade servers, o/s,
sql
> > and
> > > > > > application, and they can't see the benefit of spending that
kind of
> > > > money!
> > > > > >
> > > > > > The backwards move would be to put the application on the
platform
> > it
> > > > was
> > > > > > supposed to be on, and see if the performance issues disappear.
> > > > > >
> > > > > > Bruce
> > > > > >
> > > > > >
> > > > > > "John Bell" <jbellnewspo***@hotmail.com> wrote in message
> > > > > > news:A66A999D-2C70-4995-940A-387F58312CA4@microsoft.com...
> > > > > > > Hi
> > > > > > >
> > > > > > > You are downgrading to a product that will come to the end of
it's
> > > > life
> > > > > > > sooner than the one you are on, which can't be good. I assume
you
> > are
> > > > not
> > > > > > > paying anything for the support of this package? If the login
> > issue is
> > > > > > your
> > > > > > > only problem then I would try to find out why this happens
rather
> > than
> > > > > > hoping
> > > > > > > a downgrade will solve it. Do you get anything written into
the
> > SQL
> > > > server
> > > > > > > log or an specific error message/number?
> > > > > > >
> > > > > > > John
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > "B. Horstmanshof" wrote:
> > > > > > >
> > > > > > > > I have a sql2000 server that I am contemplating downgrading
to
> > > > sql7....
> > > > > > > >
> > > > > > > > The scenario is this:
> > > > > > > > The server was originally NT4, upgraded to Server2000.
> > > > > > > > The server ran Accountmate using SQL7.
> > > > > > > > SQL was upgraded to 2000.
> > > > > > > >
> > > > > > > > Turns out that the SQL2000 is not entirely compatible with
the
> > > > > > Accountmate -
> > > > > > > > I don't have the exact reasons why.  The application
generates
> > an
> > > > error
> > > > > > > > about a login name on startup.  The user clicks ok, then
> > continues
> > > > > > without a
> > > > > > > > problem.
> > > > > > > > The client and Accountmate reps elected to leave as is.  It
has
> > been
> > > > > > about
> > > > > > > > two years now!
> > > > > > > >
> > > > > > > > With the exception of adding data, no modifications have
been
> > made
> > > > to
> > > > > > the
> > > > > > > > databases since.
> > > > > > > >
> > > > > > > > Is it possible to do the downgrade?
> > > > > > > > What are the implications of doing?
> > > > > > > > Where would I go to get specifics to the procedure?
> > > > > > > >
> > > > > > > > Thanks in advance for any help.
> > > > > > > > Bruce.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >