Something has gone wrong!!
I've been writting ASP code for data stored in a MSSQL 7 data bank.  At 
one point I might have run some ASP code which crashed before closing a 
record set.  Then I changed some of column names and formats in three of 
my tables.  These and other tables were linked within an Access 2000 data 
bank.  I soon noticed that I couldn't erase data directly from Access.    
Access claimed too many users were trying to change the table at the same 
time. I created a simple new table in SQL and linked it to the Access DB, 
but I got the same error message.  I even made a new table in "Northwind" 
in MSSQL and linked it to the Access "Northwind", but it was read only.  
All of the old, unchanged tables (also linked) work perfectly well.  I've 
checked all the permissions and that's not the problem.  On top of all 
this, when I run the ASP programs they are now extremely slow.   The ASP 
has no problem writting to the new tables, and I can do what I like with 
them in the MSSQL enterprise manager.

Any suggestions would be greatly appreciated.  

Jim Potter

James,

Can you be a little more precise in describing what you did? In particular:
a) what did you link to what? Your description seems to indicate that you
connected SQL Server to Access, but I suspect that you actually did it the
other way around (linked Access to SQL Server)

b) what steps you actually took? Eg when you created the new table, what
permissions did you assign to the table? How did you link Access to the
table?

c) When exactly do you get the error message(s)? I suspect that you're
actually getting more than one error message (for example you'd probably get
a different error message when you couldn't delete records). What tables are
affected, and what is their structure? (perhaps you could send through a
CREATE TABLE script so we could recreate the tables on our SQL Server
databases)

d) What troubleshooting steps have you taken? For example, did you run
sp_who to see if there were any locks on any of the tables? Have you used
the SQL Server Profiler to see what is happening when you try to connect
your ASP pages to the SQL Server etc.

Cheers
Ken

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: "James Potter" <potter@e...>
Subject: [access_asp] ASP-massive slow down , Access--phony "too many users"
for new tables in MSSQL


: Something has gone wrong!!
: I've been writting ASP code for data stored in a MSSQL 7 data bank.  At
: one point I might have run some ASP code which crashed before closing a
: record set.  Then I changed some of column names and formats in three of
: my tables.  These and other tables were linked within an Access 2000 data
: bank.  I soon noticed that I couldn't erase data directly from Access.
: Access claimed too many users were trying to change the table at the same
: time. I created a simple new table in SQL and linked it to the Access DB,
: but I got the same error message.  I even made a new table in "Northwind"
: in MSSQL and linked it to the Access "Northwind", but it was read only.
: All of the old, unchanged tables (also linked) work perfectly well.  I've
: checked all the permissions and that's not the problem.  On top of all
: this, when I run the ASP programs they are now extremely slow.   The ASP
: has no problem writting to the new tables, and I can do what I like with
: them in the MSSQL enterprise manager.
:
: Any suggestions would be greatly appreciated.
:
: Jim Potter

Hi Ken,
in attempting to narrow down the source of my problem I started eliminated 
possible sources.  When using the MSSQL Enterprise Manager everything ran 
extremely slowely. So I first I backed my data bases on the MSSQL server 
and then delete.  No help. Then I deinstalled MSSQL 7 and installed MSSQL 
2000.  It still takes at least three minutes for any result from any mouse 
click.  I need about 15 minutes before I can manage to open a table 
in 'pubs' (the DB that MS delivers).  Would you have any suggestions, or 
do you know where I can go to look for an answer?

Jim


> James,

Can you be a little more precise in describing what you did? In particular:
a) what did you link to what? Your description seems to indicate that you
connected SQL Server to Access, but I suspect that you actually did it the
other way around (linked Access to SQL Server)

b) what steps you actually took? Eg when you created the new table, what
permissions did you assign to the table? How did you link Access to the
table?

c) When exactly do you get the error message(s)? I suspect that you're
actually getting more than one error message (for example you'd probably 
get
a different error message when you couldn't delete records). What tables 
are
affected, and what is their structure? (perhaps you could send through a
CREATE TABLE script so we could recreate the tables on our SQL Server
databases)

d) What troubleshooting steps have you taken? For example, did you run
sp_who to see if there were any locks on any of the tables? Have you used
the SQL Server Profiler to see what is happening when you try to connect
your ASP pages to the SQL Server etc.

Cheers
Ken

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: "James Potter" <potter@e...>
Subject: [access_asp] ASP-massive slow down , Access--phony "too many 
users"
for new tables in MSSQL


: Something has gone wrong!!
: I've been writting ASP code for data stored in a MSSQL 7 data bank.  At
: one point I might have run some ASP code which crashed before closing a
: record set.  Then I changed some of column names and formats in three of
: my tables.  These and other tables were linked within an Access 2000 data
: bank.  I soon noticed that I couldn't erase data directly from Access.
: Access claimed too many users were trying to change the table at the same
: time. I created a simple new table in SQL and linked it to the Access DB,
: but I got the same error message.  I even made a new table in "Northwind"
: in MSSQL and linked it to the Access "Northwind", but it was read only.
: All of the old, unchanged tables (also linked) work perfectly well.  I've
: checked all the permissions and that's not the problem.  On top of all
: this, when I run the ASP programs they are now extremely slow.   The ASP
: has no problem writting to the new tables, and I can do what I like with
: them in the MSSQL enterprise manager.
:
: Any suggestions would be greatly appreciated.
:
: Jim Potter

That doesn't look anything like an ASP issue, or an Access issue. It seems
that either SQL Server, or Windows Explorer is having problems.

You'll probably need to start troubleshooting your Windows installation (for
example, when using SQL Server what do the performance counters in Task
Manager tell you - is SQL Server using 100% CPU? Is it just sitting there
doing nothing? - if so, perhaps it is waiting for something - eg trying to
communicate on the network).

You might want to see if this is a problem with just Enterprise Manager, or
with other SQL Server client tools as well. If it's just EM, then there's
probably something wrong with SQL Server. If it's also Query Analyser, then
maybe you have a connectivity problem with your client-libraries or
something.

In any case, I suggest you move this onto either:
a) an SQL Server list
b) an Windows system administration list
depending on what you think the problem might be.

Cheers
Ken


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: "James Potter" <potter@e...>
Subject: [access_asp] Re: ASP-massive slow down , Access--phony "too many
users" for new tables in MSSQL


: Hi Ken,
: in attempting to narrow down the source of my problem I started eliminated
: possible sources.  When using the MSSQL Enterprise Manager everything ran
: extremely slowely. So I first I backed my data bases on the MSSQL server
: and then delete.  No help. Then I deinstalled MSSQL 7 and installed MSSQL
: 2000.  It still takes at least three minutes for any result from any mouse
: click.  I need about 15 minutes before I can manage to open a table
: in 'pubs' (the DB that MS delivers).  Would you have any suggestions, or
: do you know where I can go to look for an answer?
:
: Jim
:
:
: > James,
:
: Can you be a little more precise in describing what you did? In
particular:
: a) what did you link to what? Your description seems to indicate that you
: connected SQL Server to Access, but I suspect that you actually did it the
: other way around (linked Access to SQL Server)
:
: b) what steps you actually took? Eg when you created the new table, what
: permissions did you assign to the table? How did you link Access to the
: table?
:
: c) When exactly do you get the error message(s)? I suspect that you're
: actually getting more than one error message (for example you'd probably
: get
: a different error message when you couldn't delete records). What tables
: are
: affected, and what is their structure? (perhaps you could send through a
: CREATE TABLE script so we could recreate the tables on our SQL Server
: databases)
:
: d) What troubleshooting steps have you taken? For example, did you run
: sp_who to see if there were any locks on any of the tables? Have you used
: the SQL Server Profiler to see what is happening when you try to connect
: your ASP pages to the SQL Server etc.
:
: Cheers
: Ken
:
: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: From: "James Potter" <potter@e...>
: Subject: [access_asp] ASP-massive slow down , Access--phony "too many
: users"
: for new tables in MSSQL
:
:
: : Something has gone wrong!!
: : I've been writting ASP code for data stored in a MSSQL 7 data bank.  At
: : one point I might have run some ASP code which crashed before closing a
: : record set.  Then I changed some of column names and formats in three of
: : my tables.  These and other tables were linked within an Access 2000
data
: : bank.  I soon noticed that I couldn't erase data directly from Access.
: : Access claimed too many users were trying to change the table at the
same
: : time. I created a simple new table in SQL and linked it to the Access
DB,
: : but I got the same error message.  I even made a new table in
"Northwind"
: : in MSSQL and linked it to the Access "Northwind", but it was read only.
: : All of the old, unchanged tables (also linked) work perfectly well.
I've
: : checked all the permissions and that's not the problem.  On top of all
: : this, when I run the ASP programs they are now extremely slow.   The ASP
: : has no problem writting to the new tables, and I can do what I like with
: : them in the MSSQL enterprise manager.
: :
: : Any suggestions would be greatly appreciated.
: :
: : Jim Potter
: