Nicolas Goutte

Yes, you can do that. Activation will work too. You can just not run both Vectorworks exactly at the same time, but just alternatively. (To be sure check that the 3rd letter of your serial number is X. However as far as I know, platform-depedant serial numbers have not been issued for years. see this article from Jim Wilson: )

Thank you very much. That did it for me. It seems that 'Export Previous File Version' is the universal name, so I did not need to translate it. I hope that it can help the German user too.

A user has asked in the German forum how to call the "Export to Vectorworks 201x" menu commands from VS by using DoMenuTextByName : https://www.vectorworksforum.eu/topic/12082-export-in-ältere-vectorworks-version-via-vectorscript/?tab=comments#comment-53327 I had an idea but it did not work out. Has somebody in this forum another idea?

Using a transform matrix was what I was about to recommend, but I was unsure for a 2D-Symbol, especially in VW 2015. (However, sorry, I had no time to test it, even on a newer VW.)

Those are not parametric objects (they have not type 86 (or what is it for parametric objects)). You can check in the VWSDK, the path Include\Interfaces\VectorWorks\Objects. There are a few interfaces for simple VW objects. Your code should check the type of the object (ISDK::GetObjectTypeN) and then use the class needed for the specific object.

You should be able to use the online updater, see this post from Jim Wilson:

Does it work if you specify only one SP (be it SP2 or SP3 ?) At least the command line given in the German VW forum shows only one version number, not two: https://www.vectorworksforum.eu/topic/10341-vectorworks-2019-updater/?do=findComment&comment=52213 ) Also, as you are apparently attempting to update a Dutch VW. Are you sure that the updates are called "SP2" and "SP3" and not otherwise?

H'm, that is the first time I hear something like that. So, sorry, I cannot help you.

Locks through AFP will always behave otherwise than locks through SMB. That is totally independent of VW. See also following articles of Jim Wilson, which are not only useful in the case of project sharing. As for your other questions, sorry, I do not have any idea.

Yes, that is interiorcad's XG Resource system. All 4 screenshots are typically of problems with the XG Resource system. Indeed its folder is inside VW user folder. There are a few typical problems with non-working XG Resource system. Most of the time it will not be solved by reinstalling (especially if there is something already in the user folder, e.g. a misconfigured setting). Of course write permission problems could be there, but mostly in that case, VW itself complains if the user folder is not allowed to be written before interiorcad complains.

No, that is probably not the problem and installing it new will probably not solve it either. As the dialog tells interiorcad support should be contacted. (As this is a VW forum, not an interiorcad one, I will not get into the details.)

That is interiorcad, not VW. Therefore it is our support that you should contact.

And also see this quote: "Vectorworks 2017 & earlier: If you use a version of Vectorworks that was released prior to Vectorworks 2018, we recommend that you DO NOT upgrade your operating system, because critical bugs were introduced in the release of macOS Mojave that will affect the performance and stability of Vectorworks." From

Officially it is not supported, not even VW 2016 on macOS 10.13 is:

Alternatively, you can call "Refresh Libraries" in the Resource Manager (from the "cog wheel" menu).

I would say that if it has worked that way for you until now, then you should keep it.

Ah yes, then it is problematic. I do not know if this is the recommended way to do that or if there would be another.

I doubt that modules are loaded alphabetically. (I suppose that it is more the order in which the operating system is listing the files.) Mostly however it does not matter. You register the VCOM interfaces you define and then when really something is called in your modules, then alle VCOM interfaces are registered and you can use them.

You have to negate the internal index when setting: gSDK->SetFillPat(errorBox, -hatchIndex);

I suppose that there are no separate hardware specification, as the viewer comes from the same code base, as far as I know. Therefore I would assume that it has similar needs.

If I remember well and if I am not mixing it up with something else, you have to use -hatchIndex to set an hatch. (I cannot find back a discussion I have in mind, so probably it was a private email exchange and not a post in this forum or in the old SDK mailing list.)

Quota is a way to limit the size of files owned by a single user on a drive. So if the user trying to connect is using more than what he is entitled, he cannot write anything (probably not even a lock file). Of source, from remote, I can only guess if your are using quotas or not.

Have you quota enabled on the SMB share? That may be also a reason for "the drive is full".

You can use Batch Convert to convert lots of files from 2018 to 2019.

Sorry, but we cannot see any image in this thread. (May-be it is that what @Jim Wilson meant and why he cannot help you.)