FAQ
A Product is only entered once in VimBiz and can be a piece of equipment, a software, or a service that is accessible by any VimBiz modules. An Asset is created from a product, but has further attributes such as a barcode acting as a unique identifier. Assets are the "goods" of the company. VimBiz allows for the complete asset life-cycle management of assets and helps determine true costs of asset ownership.
Please refer to the Modifying an Existing Installation, Backing Up Your Data section.
Yes, VimBiz offers bulk importation options. Please contact Vimsoft for assistance with importation needs.
User permissions are managed in the Manage User Groups form.
Yes, via the Manage Active Directory Objects form or other methods such as explained by the Users and Permissions topic found in the Multi-User and Network Installation section of the Help Files. Please contact Vimsoft for further assistance.
The E-Mail tab needs to be filled in appropriately in the Company Details form.
Image files of type .jpg, .gif, .bmp or .png can be dragged from the user's desktop or windows explorer into an image box.
Yes, certain VimBiz forms offers that option via the context menu (right-click).
Merging Data is a quick way to get rid of duplicate entries in VimBiz.
Yes it can. VimBiz has a module dedicated to this called Interfacing. Please contact Vimsoft for further assistance.
Yes it is. A translation table is incorporated into VimBiz so users can modify existing translations to reflect more appropriate local dialects of common languages. Along with field labels, forms, tabs, and menu items, the data within fields are translated where appropriate as well. Reports generated from any VimBiz modules use the same translation table.
Yes, via the My Settings menu, Change My Font option.
By dragging a file from your desktop or windows explorer. VimBiz typically offers a button or context menu (right-click) option to insert a file as well.
The following error message, 'VimBiz Web Model was not properly configured', is normally caused by the lack of permissions for the VimDev User on the SQL server. The user should have the following permissions:
VimBiz_Formation needs permissions to operatortech
VimDev_Formation needs permissions to VimdevUser and VimdevUserFull