Map Error? DATABASE LOCKING

[Anonymous]

Hello,

we are developing app under VB for the AutoCAD Map 4.5 EN SP2.
We are using the MS SQL SERVER 7.0, throught direct or ODBC
drivers (tested also on non microsoft drivers)

When user uses the AUTOCAD SQL queries to database, then
our VB application fail when invoking the INSERT INTO command.
The SELECT command work fine. It seems that the AutoCAD MAP
locks the database, when quering and does not unlock it after use!!!!

If the AutoCAD Map SQL queries are not used, application works fine.
Tested on various cofigurations, SPacks, ODBS and OLE drivers,
the result is the same. Also tested on SQL Server 2000.

Thank you for answer,
Ondrej Novotny

[Anonymous]

Was there ever a resolution to this? I read that Map 5 resolved this,
but have not found it to be so. Any alter property sql query run via
vba locks the database. This is unfortunate because the customer
considers it crucial. It would be nice to hear something from Autodesk
on some of these issues!



On Fri, 21 Dec 2001 04:18:16 -0800, "Ondrej Novotny"
wrote:

>Hello,
>
>we are developing app under VB for the AutoCAD Map 4.5 EN SP2.
>We are using the MS SQL SERVER 7.0, throught direct or ODBC
>drivers (tested also on non microsoft drivers)
>
>When user uses the AUTOCAD SQL queries to database, then
>our VB application fail when invoking the INSERT INTO command.
>The SELECT command work fine. It seems that the AutoCAD MAP
>locks the database, when quering and does not unlock it after use!!!!
>
>If the AutoCAD Map SQL queries are not used, application works fine.
>Tested on various cofigurations, SPacks, ODBS and OLE drivers,
>the result is the same. Also tested on SQL Server 2000.
>
>Thank you for answer,
>Ondrej Novotny
>
>

[rudy.stricklan]

I am seeing this issue seventeen+ years later and I think this is still the case, at least using AutoCAD Map 3D 2020 and a PostgreSQL/PostGIS database connection. If the Map 3D connection active, then users on other software (e.g., QGIS) cannot edit the PG database. The problem is that the entire PG database is locked out, not just the schema that Map 3D has open. Kind of kills the multi-editor capability that makes PG so powerful on other software. And yes, there is a management problem when users can simultaneously edit the same features, but separating out permissions at the table level addresses this.