AutoCAD 2012 32-bit And 64-bit CRACK ONLY

0 views
Skip to first unread message
Message has been deleted

Rivka Licklider

unread,
Jul 14, 2024, 12:13:09 PM7/14/24
to ricknotmoyho

I recently setup a new desktop that is 64 bit win7 os. His old computer was 32-bit. We have reinstalled his autocad but when we open the old drawing it won't open since they were saved as 32-bit. The only solution I have found from searching is the longbow converter but this costs about 300 dollars. I was hoping that someone might have a few suggestions.

We are developing a plugin, and naturally we feel we'll need to have both a 32bit and 64bit build. The complication arises because our plugin needs to interface with Access databases (accdb), and user may have installed either 32bit or 64bit versions of Office (or the database driver). Further, it is difficult to make both the 32bit and 64bit versions of the access database driver co-exist.

AutoCAD 2012 32-bit and 64-bit CRACK ONLY


Download File https://xiuty.com/2yME6p



I mean the ODBC Microsoft Access Driver. We use Access databases partly for historical reasons (lots of legacy data) but also because they are easy for users to deal with / modify (they are user configurable databases of semi-user-specific data). It is not practical to change our database architecture at this stage.

I've managed to make this work on my dev machine by 'tricking' my 32bit Office installation into accepting the install of the 64bit driver - but doing that in the field sounds like it could be a bit of a nightmare!

When I see "it is not practical to change database architecture at this stage", I read it as "this is the only way we know, and we're afraid of the unknown". Many a developer before you has wasted a lot of time and money trying to use what they know before finally figuring out that the simple solution is to learn somethig new.

If the database is only used by your app, then you should change to a better format (like SQLite). Your end users can still use Access to edit the SQLite database via ODBC if they prefer, but it would be better if you provide a custom UI for them.

No, I mean it really isn't practical - not for technical reasons - for resource reasons (I'm perfectly conversant with other database systems). We have 2 FTEs supporting (and developing) our current product and redeveloping it for ACAD (and its complex - like 20+ years old complex...). We don't have the time or budget to change the database stuff for no real gain - SQL based systems offer us no tangible benefit over sticking with Access and only headaches for our users (many of whom struggle even to use Office)

not so long ago, we worked with Firebird in a direct way (ibpp library). but Firebird for x64 was unstable with our ibpp, because it was 32bit ))). and it was impossible to rebuild library to x64 (that's why we used 32bit Firebird in both systems 32/64bit. that was the only way to force it work). so, we desided to change "driver". in 1-2 months we ported everything we had to ADO. now, programm works pretty fine with Firebird, MSSQL. And we canadd any database our customers want in 15 minutes (the difference is just in connection string) + code rebuild ))).

there is no longer a difference in win32 and x64 for us. it's not our problem (as long as ADO live). i know, that ado is not the best way, but it's the one of the easiest (we all are little bit lazy here)

I don't know any straightforward way to do what you need but you may consider using COM to brige the plateform gap by creating a COM Win32 local server that connects to Access database (COM proxy/stub communication bridges the gap for you).

Are you saying that you need choose 32 or 64 bit AutoCAD for the user because of MS office he uses (32 or 64bit), just because of the need to access data in MS Access DB? That would be very bad and definitely "not be popular" as you expected, and very likely you do not have to.

So, as long as you are not stuck with older MS Office (2007, since it was the first version of MS Acesss that dropped MS Jet Engine and used MS Access Database Engine), you are free to choose AutoCAD 64 bit, regardless MS Office being 32 or 64 bit. Most likely, you'd use AutoCAD 64-bit. Therefore the only thing you need to make sure what your plugin requires is to install 64-bit MS Access Database Engine, which is the prerequisite of AutoCAD (64-bit), not of your Plugin (so, you do not have to feel sorry if the data access does not work in your plugin due to missing 64-bit MS Access Database Engine).

With all said, using MS Access as data sourse isn't a good choice. If your user likes the UI available in existing MS Access, you can separate the data into other type of database (SQLite, SQL Server Express...) and stiil let user to use the same MS Access UI, and AutoCAD can access the data direcctly to the back end. Better yet, the backend data may be wrapped into a backend web service, so the 32/64 (or future "128 bit" :-)) issue can be gone forever.

The main probelm bit wise is if the user has 64-bit AutoCAD and 32-bit Office. Office installs the Access Database Engine, so you end up with the 32-bit version. You can't then install the 64-bit Access Database Engine without resorting to "trickery" (using the /passive command line parameter and fiddling with a registery entry). I'm not that comfortable relying on trickery - even if it does seem to work...

If you cannot change the fact that the data has to ne in MS Access database and be "ordered" to deal with it, as a customization programmer, you can wrap the data source in a service hosted in your network, or even the cloud, so that AutoCAD will access data data via the service and knows nothing the data source format (be it MS Access, Excel worksheet, Sql Database...).

By default on 64bit operating systems AutoCAD will be 64bit too. But there are installers which can install a 32bit AutoCAD in an 64bit operating system ... and so the folder itself does not tell you anything.

I tried getenv command in 2019 but it doesn't seem to exist. Any other options for 2019? I thought I was running 64 bit, but my task manager shows some 32 bit security processes running under the application, and cad keeps hanging up every few commands. Maybe a compatibility issue?

The problem started after I installed 2021 which would just randomly completely freeze up and wouldn't even let me get to task manager to end process. I read threads that others had the same issue with no solution so I went back to use 2019 which now doesn't work, and I have to reload my profile every time I open it.

@pendean Excuse me, is there really no option to install 32-bit AutoCAD in 64-bit Windows? I tried to download AutoCAD from here, and though I have 64-bit Windows, a 32-bit version of the app was downloaded, and now I can't install it

Yes @Anonymous, it's hard to understand your problem. This thread is about the 2014 release and figuring out how many bits the system has so that the appropriate version can be downloaded. It's practically ancient history.

I understand that basic non COM applications compiled in VS using "Any CPU" as the target CPU will run in both 32bit and 64bit. At least in AutoCAD 2011 and above. I also understand that the MS Jet connector will not run in 64bit mode.

So... I (among others) need some advice when it comes to working with database connections in BOTH 32bit and 64bit. I am wondering if we can get some dialog going to provide a complete and accurate solution for the many of us that have (or will have) these requirements.

My personal requirement is this: We are an all 32bit (XP) office with plans to upgrade every machine to 64bit (Win 7) over time. The first 64 bit machine will be rolled out in less than two weeks. It will take us the better part of two years to completely upgrade all of the office machines. Obviously we will need to have custom .NET applications running long before the computer upgrade process is complete.

I have an Access database that I need simple connectivity to inside of AutoCAD. I am basically populating controls with contents from certain fields in the tables of the database. I do not need to make any changes to the database from AutoCAD (at this point in time). The Access database will be used by others outside of AutoCAD. The database will be updated on a regular basis by users outside of AutoCAD, so I am not sure if changing from Access is an option.

Your issue is mainly regarding using Access database (*.mdb/*.accdb) with 64-bit OS and 64-bit AutoCAD, not a generic "database". If you use a server type database, such as SQL Server, MySQL, you would not have this issue.

There are two type of Access database since the release of MS Access2007/MS Office 2007. All Windows OS come with MS Jet Engine installed, which the component that provides access to data stored in MS Access database (*.mdb file) until MS Access 2007. That is, one can write applications that access data stored in *.mdb file without installing MS Access application, because the application uses DAO/ADO in conjunction with Jet Engine to access/query data in *.mdb file.

Then, starting from MS Access 2007, a new database engine is used (MS Access tabase engine), instead of Jet Engine. Originally, this database engine only comes with MS Access installation, meaing, you cannot access data in the *.accdb file unless you install MS Access application. This caused outcry of course, and later MS made MS Access Engine (for MS Access database 2007 and later) a free download, so the data in *.accdb then can be manipulated by custom apps as in *.mdb. However, the new database engine must be explicitly downloaded in installed, if the computer does not have MS Access installed.

Also, The free download of MS Access database engine is back-compatible, meaning it can be used to access not only database created by MS Access2007 (*.accdb), but also earlier Access version (*.mdb). The same as Jet Engine, it can also be sued to access data stored in Excel sheet without opeing it in Excel application.

b1e95dc632
Reply all
Reply to author
Forward
0 new messages