furtivevole
Technical User
I have an application that includes a number of separate .asp pages, each of which writes (on opening) to a particular table on an Access db held in the same FrontPage web. There is no read or modify of existing records.
In the past (up to last June) I've been able to modify the design of the db. Needing to do this again this week, I'm now getting a message: "You can't open the table <name> for modification. A query or form bound to the table is open, you may not have permossion to open this table in Design view, or another user has the table open... etc"
This occurs even when (a) no-one else is using the system - no .ldb file around - (b) only the database window is open, no other forms, queries etc. and (c) permissions appear OK. If I copy the db, the problem moves with it. If I re-create it by setting up a blank db and copying each table etc individually, I can then get into design mode until such time as I've then opened one of the .asp pages. The rs.update is apparently the trigger that prevents me from using design mode (though the write itself is OK). This persists even after the session timeout (30 minutes). Other tables that are not used by the .asp pages are OK.
I've migrated from NT to W2K in the interim, though I don't expect that this would affect permissions etc at table level. The server-side vbscript that handles this has been stable for a long time.
Has anyone had a similar experience?
TIA, Linnet
In the past (up to last June) I've been able to modify the design of the db. Needing to do this again this week, I'm now getting a message: "You can't open the table <name> for modification. A query or form bound to the table is open, you may not have permossion to open this table in Design view, or another user has the table open... etc"
This occurs even when (a) no-one else is using the system - no .ldb file around - (b) only the database window is open, no other forms, queries etc. and (c) permissions appear OK. If I copy the db, the problem moves with it. If I re-create it by setting up a blank db and copying each table etc individually, I can then get into design mode until such time as I've then opened one of the .asp pages. The rs.update is apparently the trigger that prevents me from using design mode (though the write itself is OK). This persists even after the session timeout (30 minutes). Other tables that are not used by the .asp pages are OK.
I've migrated from NT to W2K in the interim, though I don't expect that this would affect permissions etc at table level. The server-side vbscript that handles this has been stable for a long time.
Has anyone had a similar experience?
TIA, Linnet