"Ragnar Midtskogen" <ragnarm@optonline.net> wrote in message
news:e9cWJMgVDHA.2272@TK2MSFTNGP11.phx.gbl...
> Hello,
>
> I have an Access 2000 application wich uses SQL Server linked ODBC tables
> running on Windows 2000 Pro, with the SQL Server running on Widows 2000
> Server..
> It is a multi-user system with up to 5 users, connected to the server
> machine through a Samba network.
>
> The application has worked well with Access as the back-end for almost 8
> years, but the amount of data was slowing the response, so I recently
> converted to SQL Server. Now the users are having unexpected problems with
> several Yes/No fields.
> The application has not changed, just the linking to the back-end.
>
> Some times, after entering a record, then trying to edit the record, all
the
> checkboxes based on Yes/No fields show up as being set, although only one
or
> two were set originally.
>
> Another peculiar error is when a checkbox is set then cleared before the
> record is saved. When editing the record the cleared checkbox shows up as
> set, but if it is cleared then saved, it stays cleared.
>
> A third problem has to do with a combo that is normally disabled. It is
> enabled when the user sets a checkbox by clicking it. Now, sometimes the
> combo is enabled when the form shows an empty record.
>
> The forms are unbased, DAO recordsets are used to copy data from the
tabled
> to the forms and to update the tables with the data in the forms.
>
> All the SQL Server tables have a primary key.
>
> I had tested the application thoroughly at the office, using the same
> platforms as the client is using, before deployment and everything seemed
to
> work fine.
> I can reproduce the error with checking then unchecking the checkbox but
not
> the other problems.
>
> Any comments or suggestions would be very much appreciated.
>
> Ragnar
>
>

> AFAIK, Access stores boolean datatypes differently than SQL Server. There
> are issues to be resolved if your yes/no Access field became a bit column
in
> a SQL Server table. Again, a NG search should get much more information

"Scott Morris" <bogus@microsoft.com> wrote in message
news:e8DCJqpVDHA.2344@TK2MSFTNGP09.phx.gbl...
> Have no particular solution for you - but these are the things that I have
> noticed over the years just by reading NG messages.
>
> Usually most problems have already been discussed in the appropriate NG.
> Google http://groups.google.com/advanced_group_search?hl=en be used for
> searching (in this case, the .programming NG is the first choice). In
> particular, search/read posts from Mary Chipman, who appears to be very
> knowledgeable about Access/sql server issues.
>
> AFAIK, Access stores boolean datatypes differently than SQL Server. There
> are issues to be resolved if your yes/no Access field became a bit column
in
> a SQL Server table. Again, a NG search should get much more information.
>
> "Ragnar Midtskogen" <ragnarm@optonline.net> wrote in message
> news:e9cWJMgVDHA.2272@TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I have an Access 2000 application wich uses SQL Server linked ODBC
tables
> > running on Windows 2000 Pro, with the SQL Server running on Widows 2000
> > Server..
> > It is a multi-user system with up to 5 users, connected to the server
> > machine through a Samba network.
> >
> > The application has worked well with Access as the back-end for almost 8
> > years, but the amount of data was slowing the response, so I recently
> > converted to SQL Server. Now the users are having unexpected problems
with
> > several Yes/No fields.
> > The application has not changed, just the linking to the back-end.
> >
> > Some times, after entering a record, then trying to edit the record, all
> the
> > checkboxes based on Yes/No fields show up as being set, although only
one
> or
> > two were set originally.
> >
> > Another peculiar error is when a checkbox is set then cleared before the
> > record is saved. When editing the record the cleared checkbox shows up
as
> > set, but if it is cleared then saved, it stays cleared.
> >
> > A third problem has to do with a combo that is normally disabled. It is
> > enabled when the user sets a checkbox by clicking it. Now, sometimes the
> > combo is enabled when the form shows an empty record.
> >
> > The forms are unbased, DAO recordsets are used to copy data from the
> tabled
> > to the forms and to update the tables with the data in the forms.
> >
> > All the SQL Server tables have a primary key.
> >
> > I had tested the application thoroughly at the office, using the same
> > platforms as the client is using, before deployment and everything
seemed
> to
> > work fine.
> > I can reproduce the error with checking then unchecking the checkbox but
> not
> > the other problems.
> >
> > Any comments or suggestions would be very much appreciated.
> >
> > Ragnar
> >
> >
>
>