I don’t have the correct terms for the licenses but it’s like this:
We have a license for DMS that allows full functionality on the jump server, including the generating of toolpaths. Our DMS installation is (for obvious reasons) locked down and we can’t make persistent changes to the tool database. Allowing that would soon result in a much worse situation than the one that exists.
We have licenses for “home” versions that are fully functional except that they won’t generate toolpaths. With a home installation, we can obviously make all the changes we want to our tool databases, however…
The DMS installation and “home” installations are different versions of VCarve, so the files created at home are incompatible with, and can’t be opened by, the copy at DMS.
As for the tool databases (home versus DMS), there is no way to simply “open” a private tool database and use the settings from that. VCarve only has an “import” function which merges the tools in a database with the ones in the DMS installation. Due to the “locked-down” nature of the DMS installation, such an import will not work (or at least won’t be persisted - I haven’t dared to try it).
So given all of the above, your only reasonable option is to use the DMS copy of VCarve to create your entire job (can be done using Remote Desktop), pick standard library tools and tweak their settings to match your bits.
IF feeds/speeds are stored in the VCarve file (meaning your project file) and don’t depend on a particular tool database AND we get the installation versions in sync, then theoretically projects created at home could be opened at DMS and toolpaths generated with no friction.