|
Q: How to manually create a Pervasive Server Engine DSN (Data
Source Name)?
A: Perform this procedure on your database server if you are
having difficulties using the PowerTools
automatic DSN creation function.
Upgrades to Pervasive typically break existing ODBC connections and they must be deleted and re-created.
MK PowerTools requires a fully operational Pervasive ODBC database connection to work, it is the end-users responsibility to create and maintain the database, computers and network environment.
BusinessVision uses basic Btrieve data access whereas PowerTools utilizes the industry standard Pervasive SQL interface.
Because you can access data through BusinessVision, it does not prove Pervasive SQL is installed, operational or configured correctly.
- From the console of the database server, open the Pervasive Control
Center from the Start Menu / Programs
/ Pervasive / PSQL.. folder.
- Expand Engines, expand
your Computer Name, then right-click
on the Databases container, and select
New and then Database.
- Database Name: Enter a meaningful name for this
database, keep it simple, less than 8 characters and
no spaces (For example ABC)
- Location: Here, enter the "Physical
Path" to your BusinessVision data files. THIS IS VERY IMPORTANT! The physical path
is the hard-disk path (not the logical or
mapped drive path or UNC path). For
example if your server had
a data drive identified as E:\ then the physical
path would be something like (e:\bvdata\abc).
- Click Finish.
The basic database is now created, now we must go back to the database properties and edit
the Dictionary Path.
- Under the Databases
container, select the newly created
database "ABC" then right-click and select
Properties.
- The Database properties window will open
and select the Directories menu
on the left pane.
- On the Directories page, click on the end of the Dictionary Location
string and append "\mks" to
the path (Don't type in the ""). So the
full dictionary
path should look like [e:\bvdata\abc\mks]. PowerTools will automatically maintain and update the DDF files in that path location
- Click OK button.
Now we can test the database.
- Now drill down or expand the new
database ABC by using the [+] and you
will see Tables. Expand
Tables and you will see all your
BusinessVision database tables in SQL view.
- Locate a simple table that should have
data in it such as "ADDRESS",
double-click on it and you should be able to
see data load in the right pane.
- Note: This setup assumes you have tried to add
the DSN from the client and that PowerTools
has copied the DDF files to the \mks
directory (which it does automatically). If not try to add it from
the client again or create the folder
manually and copy the DDF from
BusinessVision CD or the PowerTools\support\BVxx program
folder. If you still have issues,
double-check the instructions to see if you
missed a step. If all looks ok and you
are getting errors then perhaps look at
reinstalling your Pervasive Engine, there is
an FAQ on how to do this.
Back on the Client PC, MK PowerTools should be able to detect the Pervasive Server Engine DSN and setup
your Pervasive ODBC Client DSN connection automatically.
If PowerTools scans your server and cannot detect your Server DSN and you are sure you have followed the steps correctly then your likely have a problem with you Pervasive installation.
As a final step, you may try to manually create the Pervasive ODBC Client DSN by opening the 32bit ODBC Administrator.
[back to top]
Q: How to install PowerTools SQL on Microsoft
Terminal Server / Citrix?
A: The following applies to all Terminal Server
platforms, 2000 and 2003 server. At the core,
Terminal Server and Citrix are the same so the language
in this document is interchangeable.
You must follow these instructions 100% otherwise
your setup will fail 100% of the time and
PowerTools will never work.
Firstly, you must perform both the installation
and setup the connection to your
BusinessVision company on the PHYSICAL CONSOLE of
the Citrix Server. The PHYSICAL
CONSOLE means you are sitting in-front of the monitor,
keyboard and mouse that is
connected to the server. If you are not able to
connect to the Physical Console, don't bother
going further**. If you are logging in through a
Terminal, Citrix or Remote Desktop**
connection this DOES NOT WORK EVEN IF YOU ARE LOGGED
IN WITH THE ADMINISTRATOR
ACCOUNT! (This is not a PowerTools limitation but
a Pervasive.SQL limitation). Once you have
successfully connected MK PowerTools to your BusinessVision
database, users can then login
and run PowerTools through virtual sessions.
Secondly, if your Windows users are part of the
local Windows "Users" group then you must
give the Windows local users group "change permissions"
on the PowerTools program folder,
sub-folders and files, usually found in C:\Program
Files\MK PowerTools. Consult Microsoft help
on setting file and folder permissions.
**TIP: With Windows 2003 Server, you are able
to shadow the physical desktop session of
the server as if you were sitting at the console.
You must use either another Windows 2003
Server's Remote Administrator program with the console
switch checked or use Microsoft
Remote Desktop executed from a command line. To
use Remote Desktop or RDP, create the
connection and save it to "c:\server.rdp", then
from the command line or batch file execute
the following string without the "". "mstsc c:\server.rdp
-console". The monitor on the Server
will display CTRL ALT DEL while the remote is using
the console session and the physical operator can
access the desktop by simply logging in.
Q: How to fix "Product Signatures in reference do not match" when activating or renewing?
A: Close MK PowerTools, using Windows Explorer, navigate to the MK PowerTools program folder on the file system.
Typically (C:\Program Files\MK PowerTools) and delete the folder
5356-8651-2429-7641-5702
Restart MK PowerTools and the activation process should work.
[back to top]
Q: How can I optimize
my network environment to run BusinessVision?
A: BusinessVision utilizes Pervasive and the key components are the Client Requesters
and a Server Engine where the data is located. BusinessVision Standard and Client-Server
Edition
systems are more or less identical in operation
with the exception that Pervasive NT Server
includes more performance resources and is
licensed for more users.
The only computer(s) on your network that
require the installation of the Pervasive Server
Engine or Workgroup Engine are the ones with data
files located on physical machine or in rare
cases when the computer serves as a "gateway".
The BusinessVision program installs the
Workgroup Engine by default to make it
convenient for users to access the DEMO data on
the local machine and learn to use the software
(C:\BusinessVision\demo).
In a typical network environment, the
Workgroup engine installed on the client
stations can be turned off saving workstation resources
and eliminating gateway delegation issues.
In other words you don't to be running database
servers on all your workstation to run BV or
PowerTools or any other 3rd party program unless
it is poorly designed.
Turning off the Engine on the client should
free up about 25-30MB or memory and help your
machines boot-up and shut-down faster.
The Pervasive Client components are ALWAYS
installed with ANY Pervasive.SQL installations.
Here are the simple steps to disable the Pervasive
Workgroup Engine:
- Open the Pervasive.SQL Control Center
and drill down to "Local Client" and then "Microkernel
Router".
- Under the "Access"
page, remove the check
on "Use local Microkernel Engine" and that will
turn it OFF.
- Delete the Pervasive Workgroup Engine shortcut
from the Start Menu / Programs /
Start-up folder. Or with Pervasive 10, go to
Windows Services and set the service startup
to Disabled and stop it.
- Shut down the Workgroup engine running in
the system tray if it is running.
- There are some minor exceptions to
consider, for example if you edit Crystal
Reports and require access to manipulate the
DDFs in the reports then you should turn the
local engine back on as required.
[back to top]
Q: Does Inventory
Code Change or Merge modify my sales history or
Bill of materials?
A: Yes, PowerTools modifies all current and historic
databases including Sales Orders, PO, BOM,
Sales History, Inventory Receipts. You system works
as if you have been using the new part
number since day 1.
[back to top]
Q: Can I Un-issue
a Purchase Order that has been fully or partially
received?
A: Yes, PowerTools will allow you to make changes
to POs that have partial or full receipt of some
or all items. All information is retained with the
Purchase Order when it is re-issued.
[back to top]
Q: How does PowerTools
SQL access my BusinessVision database?
A: PowerTools connects to your BusinessVision
database utilizing the Pervasive.SQL relational
interface or otherwise known as ODBC (Open Database
Connectivity).
ODBC is a API (Application Program Interface) standard
used to communicate with a
Relational Databases such as Microsoft SQL Server,
Informix, IBM, Oracle or Pervasive.SQL to
name a few. SQL is the industry standard
for data access.
SQL (Structured Query Language) is a high level
database language used to talk to a
Relational Database. MK PowerTools SQL leverages
this high-level language whereas
BusinessVision uses a lower-level Btrieve API.
There are 2 key reasons why using the SQL interface
is preferred.
- Database Integrity. SQL features automatic
transaction roll-back, this way if any
PowerTools process does not complete from start
to finish, terminates unexpectedly,
power failure, database issue, whatever; all
transactions are automatically rolled-back
and no information what-so-ever is modified
in your database. You will never have
partially completed entries or processes.
- Superior Database Performance. In a
Client-Server environment, the SQL commands
are sent to the Server and executed on the
Server rather than over the network,
eliminating network latency. Try
rebuilding a file over the network then on
the server and you'll see the speed
difference.
PowerTools SQL leverages all benefits of the
Pervasive.SQL Server Engine.
So why doesn't BusinessVision use SQL?
BusinessVision is written in Microfocus COBOL
programming language that is designed to bind to
ISAM database files. Originally BusinessVision
used COBOL ISAM database files and because
Btrieve ISAM files were superior to COBOL and
the migration was more or less seamless from a
coding perspective the switch was made to
Btrieve some 10 years ago. ISAM files were
once ideal for high-volume OLTP systems because
the technology was lightweight and computers
were slow relative to today's modern systems and
networks. Btrieve was a Novell
product/technology and was spun-off in the late
90's to form Pervasive and an SQL interface was
developed to add a relational interface to the
Btrieve database.Some Sage programs that use
Pervasive.SQL include Sage Accpac ERP, Sage PFW,
Sage BusinessWorks and programs that use Btrieve
API are BusinessVision and Peachtree by Sage for
example.
[back to top]
Q: Can I run
PowerTools while other users are logged into BusinessVision?
A: Yes and No, the Search and Replace Code Change
and Merge tools will lock some files
during the process. G/L Account Code Change and
Merge will definitely lock the
BusinessVision Control File preventing any user
from processing transactions, logging on, etc.
For these programs, it is best to queue your change
list and run it after hours when you go
home at day end.
Most other PowerTools programs can run concurrently
with BusinessVision.
[back to top]
Q: What are the
system requirements for running PowerTools SQL?
A: BusinessVision version 7.x or later, Pentium
II or better, minimum of 64MB of RAM, 50MB
of free disk space, Pervasive.SQL 9.x and later.
[back to top]
Q: How do I fix License error
23?
If you receive license error
23 either the MK Software Edition you are running
is not compatible with your BusinessVision license,
or your BusinessVision system is incorrectly reporting
the number of user licenses.
MK Software Small Business
Edition license is valid for BusinessVision 5 user
systems, Business Edition is licensed for BusinessVision
10 user systems and Corporate Edition is licensed
for BusinessVision Client-Server 20 user or more.
If your license is not valid, you are required to
upgrade your MK Software license edition.
The cost of the upgrade is approximately the difference
between the two editions.
If your edition is valid, it
may be possible that BusinessVision has inserted
the incorrect number of license files in your BusinessVision
database directory. Browse to your data directory
and check the files WDSAMXX.NUM. For example,
if you are using a Small Business Edition which
is a 5 user license, then you should only have WDSAM01.NUM
up to WDSAM05.NUM in your data directory.
Remove the files WDSAM06 and up then restart the
MK PowerTools application.
[back to top]
Q : How to Completely
remove Pervasive.SQL from your system?
Use this procedure if you are upgrading Pervasive,
or if you are having technical problems
with Pervasive that cannot be resolved,
or if you are or if instructed to do so by technical
support:
- Login to your computer with Administrator
permissions
- Shut-down any Pervasive Engine running on
the local computer.
- Run the Microsoft ODBC Administrator,
select run and odbcad32 or browse to it
under Administrative Tools, Data Sources ODBC.
- In ODBC Administrator, go to the System
tab and note the setups for
Pervasive ODBC Connections that must be
manually re-created. PowerTools
creates the database automatically so you
can just delete them and add them back using
the PowerTools interface.
- Remove each data source name using the remove button and close the
ODBC Administrator.
- Go to Control Panel, Add/Remove Programs
and uninstall any Pervasive Software
programs.
If prompted to remove license keys and settings,
say yes.
- Delete the Pervasive program folder on your
local hard disk, this is usually at C:\PVSW.
- Run Registry Editor by going to the Start
Menu, Run and type regedit, then press enter
or OK.
- Delete the registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software".
See Microsoft
documentation on saving / backing up registry
keys.
- Pervasive also leave behind all sorts of
environment value setup in system, go there
and clean those entries from path and so on.
Anywhere you see PVSW. BusinessVision
recommends using the Pervasive Analyzer to
clean up the system, you can try that too.
- Reboot and re-install Pervasive from your
BusinessVision CD-ROM.
It is also advisable to read the BusinessVision
Installation Manual for more info on implementing
Pervasive.SQL.
- Start PowerTools and if existing
connections were setup, PowerTools will
automatically recreate the connections.
[back to top]
Q : How to resolve Error 3146-ODBC
Call Failed?
A: Try to move your data to
another machine, usually on local workstation (but
if you are running an Engine DSN, it will make no
difference, in that case, try another machine).
If it works, that proves it is a Pervasive problem.
70% of these errors are caused
by a malfunction in the Pervasive DB environment
and can only be resolved by complete un-installation
and re-insallation of the database engine. See the
instruction on "How to completely remove Pervasive.SQL
from your system" for details.
If you still have a problem,
you need to send your data to our network via FTP
and we will test it for debugging.
[back to top]
Q : How to resolve "Invalid procedure
call or argument" error when launching MK PowerTools?
A: Try to uninstall MK PowerTools
and delete the entry in HKEY_LOCAL_MACHINE\SOFTWARE\MK
Software in the registry. Then download the older
version of the MK PowerTools from the website (http://www.mksoftware.com/download/MKPT725FULL.exe).
This version of MK PowerTools includes MDAC and
other components that are supposed to be part of
the Windows 2000 sp4 and later.
After installing the older
version of the application, download the latest
release of MK PowerTools and install.
[back to top]
|
