remove 10 000 records limit

Hi,
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted afte
r
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
ThanksHere's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.

> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutc
h)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
--
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:

> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted af
ter
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
[vbcol=seagreen]
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in du
tch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:
>

remove 10 000 records limit

Hi,
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted after
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
ThanksHere's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutch)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
--
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in dutch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:
> > Hi,
> >
> > Our users that connect to a MSSQL db via MS-Access cannot access more than
> > 10 000 records. In other words, all the records that have been inserted after
> > the 10 000th record cannot be access nor from the table, nor from a query.
> >
> > Is there any way to overcome the problem?
> >
> > Thanks

remove 10 000 records limit

Hi,
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted after
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
Thanks
Here's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.

> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.
|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks
|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutch)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:

> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks
|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
[vbcol=seagreen]
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in dutch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:

Remote View Question

I am connecting through EM to another SQL server for my web
site, is there a way to limit it so that I only see my database and
not all the 100's of others that are listed.

Also, sorry if this sounds dumb but I applied the sp3 sevice
pack and I dont know how to verify this, normallly one would go to
help>about and see it there, there was a sp3 and a sp3a, but a
friend told me to only apply the sp3, needless to say it seems slow
connecting and I would like to verify that everything is in working
order.

Thank You

Reply to newsgroup as email address is bogus due to spam

MichaelIn the query analyzer run the command: @.@.version. When your version
numbver shows 8.00.760 SP3 is installed. Have a look at this website:
http://www.krell-software.com/mssql-builds.htm for all version numbers
of sql-server.

There is no reason not to install SP3a !!!

Hiding database in the EM is just not possible:

"There is not a way to hide the databases in Enterprise Manager. It
does not
have that capability. The database listing comes from the sysdatabases
table and there is no way to filter the data to hide the databases the
user
does not have access to"

Greetings Sjaak|||MiKeY <Mikey@.yahoo.com> wrote in message news:<anhksvc3gnc041ib7snqh6chbgnpttlrhd@.4ax.com>...
> I am connecting through EM to another SQL server for my web
> site, is there a way to limit it so that I only see my database and
> not all the 100's of others that are listed.
> Also, sorry if this sounds dumb but I applied the sp3 sevice
> pack and I dont know how to verify this, normallly one would go to
> help>about and see it there, there was a sp3 and a sp3a, but a
> friend told me to only apply the sp3, needless to say it seems slow
> connecting and I would like to verify that everything is in working
> order.
>
> Thank You
> Reply to newsgroup as email address is bogus due to spam
>
> Michael

EM always displays all databases on the server; QA displays only the
ones you have access to. But connecting with QA probably won't be any
faster, because it has the check all databases to see if you can
access them. From the server side, if any databases are set to
autoclose, then populating the list in EM can be very slow, but if you
are not the DBA or if the server is with an ISP, then there's probably
not much you can do about that.

As for identifying the servicepack, on the client you can check the
version number in Help-About in QA; for the server you can check this
KB article:

http://support.microsoft.com/defaul...b;en-us;q321185

Simonsql