VMVendor Broken with Newest VirtueMart Update 03-03-2021

Hello
Sorry for the late reply, I'm back from a one week trip.
Let me know your exxact VM version, and I'll investigate the issue and provide a new VMVendor version ASAP.
Thank you for your patience.

Hello
I made a fresh install of Joomla, com_virtuemart.3.8.8.10472_package_or_extract
and current VMVendor.
I can't reproduce that error as VM correctly installed the #__virtuemart_vmusers table with that virtuemart_vendor_id column.

So it seems that you are missing it on your setup, but Recent VM still installs it.

If you don't have it you could run this query in phpmyadmin:

FIRST backup your whole database so can't blame anyone for a mistake

ALTER TABLE #__virtuemart_vmusers ADD `virtuemart_vendor_id` int(1) UNSIGNED NOT NULL DEFAULT '0' AFTER `virtuemart_user_id`;

ALTER TABLE #__virtuemart_vmusers ADD CONSTRAINT `virtuemart_vendor_id` KEY (`virtuemart_vendor_id`);

For your information here is the table structure:
CREATE TABLE IF NOT EXISTS `#__virtuemart_vmusers` (
`virtuemart_user_id` int(1) UNSIGNED NOT NULL AUTO_INCREMENT,
`virtuemart_vendor_id` int(1) UNSIGNED NOT NULL DEFAULT '0',
`user_is_vendor` tinyint(1) NOT NULL DEFAULT '0',
`customer_number` varchar(32) DEFAULT NULL,
`virtuemart_paymentmethod_id` int(1) UNSIGNED DEFAULT NULL,
`virtuemart_shipmentmethod_id` int(1) UNSIGNED DEFAULT NULL,
`agreed` tinyint(1) NOT NULL DEFAULT '0',
`created_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`created_by` int(1) NOT NULL DEFAULT '0',
`modified_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`modified_by` int(1) NOT NULL DEFAULT '0',
`locked_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`locked_by` int(1) NOT NULL DEFAULT '0',
PRIMARY KEY (`virtuemart_user_id`),
UNIQUE KEY `u_virtuemart_user_id` (`virtuemart_user_id`,`virtuemart_vendor_id`),
KEY `virtuemart_vendor_id` (`virtuemart_vendor_id`),
KEY `user_is_vendor` (`user_is_vendor`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Holds the unique user data';
COMMIT;

PS make sure you replace #__ with your own table prefix.

Hope it helps. Let me know.