| DBA Services Home Page
|
|
DBA
ODBC White Paper
Operating System
Requirements
Windows 95, 98, NT at your workstation(s). If you have a network
server, Windows NT or Novell Netware at your server.
Back to top
Pervasive Software
Requirements
You must be running either DBA Client/Server or, if you are running a
DBA Peer-to-Peer system, have installed the Pervasive SQL.2000 Workstation Engine. Is you
are running a DBA Peer-to-Peer system and are not running Pervasive.SQL Workstation
Engine, contact DBA Software.
Pervasive Software ODBC-32- version 2.53.0300 or higher. The ODBC
driver shipped with DBA’s Client/Server version prior to version 99.2 and was
installed during a typical installation of Pervasive SQL 7. The Pervasive ODBC
Engine Interface and Pervasive ODBC Client Interface drivers, version 7.5X.XXXXX, are
installed with the Pervasive SQL.2000 Client/Server and Peer-to-Peer versions. The
steps for configuring a new data source discussed below are different depending upon the
driver and Pervasive SQL version you have installed (i.e. version 2.5X.XXXX or
7.5X.XXXXX). To verify the driver and version you have installed check the 32 Bit
ODBC Administrator found in your Control Panel or in your Pervasive SQL 7 or Pervasive
SQL.2000 folder.
Back to top
DBA Accounting
/ Manufacturing / Distribution Software Requirements
DBA version 98.1 or higher.
ODBCDDF.RUN dated 11/10/98 or later found in your DBA program
directory. ODBCDDF.RUN as of version 99.1 will not work with DBA MS Access ODBC Reports.
DBA plans to ship the more recent version in future releases.
Because ODBC requires its own set of DDF files, your default company must
be located in a separate folder located beneath your DBAMFG folder.
Earlier versions of DBA did not separate the default company from the DBAMFG program
directory.
Start DBA, switch to the company(s) you would like to use ODBC
reporting with, and run ODBCDDF from UT-A.
Back to top
Configuring a
New ODBC Data Source (Pervasive
7 - Version 2.5X. XXXX)
Start the ODBC 32 Bit Administrator from the Control Panel or
Pervasive SQL 7 folder.
Select System DSN and click Add.
Select Pervasive Software ODBC-32 and click Finish.
Enter a name for your Data Source and then Browse to the location of
your company data. Double click on FILE.DDF located in your DBA Company data directory.
Select Access/Jet Compatibility.
Click OK.
Repeat the steps for additional companies for which you would like
ODBC Connectivity.
Your completed screen will look as follows. Click OK and close
the ODBC Administrator.
Back to top
Configuring
a New ODBC Data Source - (Pervasive SQL.2000)
NT Server/Workstation
Engine
Note - These procedures apply to all SQL.2000 Peer-to-Peer Workstations
and to the NT Server only for a Client/Server installation.
To use ODBC at an NT Server, the Pevasive Relational Service must be
running. To verify the Pervasive Relational Service is running at your NT Server,
check Services from the Control Panel of your Server.
At the NT server, start the ODBC 32 Bit Administrator from the
Control Panel or Pervasive folder.
Select System DSN and click Add.
Select Pervasive ODBC Engine Interface and click Finish.
Enter a name for your Data Source.
Click Create under Database.
Enter a name for your Database and enter the path to your DDF files
under Dictionary Location and Data File Locations. Use the Browse and Add buttons.
Check Integrity Enforced.
Click OK
Your completed screen will look as follows. Click OK and close
the ODBC Administrator.
Back to
top
NT Client
Note - These procedures apply to all SQL.2000 Win 95, 98, or NT
workstations for an NT Client/Server installation.
At the Win 95, 98, or NT workstation, start the ODBC 32 Bit
Administrator from the Control Panel or Pervasive folder.
Select System DSN and click Add.
Select Pervasive ODBC Client Interface and click Finish.
Enter a name for your Data Source.
Enter your server IP address or name under Server Address.
Click Get DSN List and select a Data Source Name. This is the
same name you created at your server using the Pervasive ODBC Engine Interface (See Creating a New ODBC 7.5X.XXXXX Data Source - NT
Server).
Your completed screen will look as follows. Click OK and close
the ODBC Administrator.
Back
to top
Novell
Netware Server and Client
Note - These procedures apply
to all SQL.2000 Win 95, 98, or NT workstations for an Novell Netware Client/Server
installation.
To use ODBC on a Netware Server, the Pevasive Relational Service must
be running. To verify the Pervasive Relational Service is running type MODULES at
the server console and verify the engine to be loaded or run MGRSTART at the server.
Create the system DSN on the client machine to the data on the
Netware server. For Novell users, the client interface creates an Engine Interface
DSN.
At the Win 98, Win 95, or NT workstation, start the ODBC 32 Bit
Administrator from the Control Panel or Pervasive folder.
Select System DSN and click Add.
Select Pervasive ODBC Client Interface and click Finish.
Click Connect and enter your server name under Connecting to and
enter your normal User name and Password.
The Pervasive ODBC Engine Interface DSN Setup dialog box is
displayed.
Create an Engine Interface DSN (see NT Server/Workstation Engine) and click OK.
The Pervasive ODBC Client Interface DSN Setup dialog box is
displayed.
Create a Client Interface DSN (see NT Client)
and click OK.
Back to
top
Starting
Microsoft Access and Connecting to Your Data Source
We suggest you download
DBA Connection Manager, open in Microsoft Access, and click Help. This tool will
greatly assist you in establishing and managing your ODBC connections.
Special Note
The first time you run DBA MS Access ODBC Reports after installation,
or after creating a new set of DDF files and ODBC Data Source, you may receive MS Access
and ODBC errors (for no apparent reason that we can find). Restarting Windows will cure
the problem.
Back
to top
ODBC and Security
Some users are concerned that DBA data can be modified and deleted
without any password protection. The ability to modify and delete data is actually a
benefit and can come in quite handy at various times. But the fact is Microsoft
Access has one of the finest security systems available which, if set up properly, is
virtually impossible to break. Refer to your Microsoft Access documentation, help files,
and the Microsoft web site for detailed procedures on setting up security.
Security must be set AFTER attaching your DBA tables and must be
created at each site where DBA is implemented. Most users do not like the hassle of
security due to logon screens, passwords, and the extra cost associated with
administration. Evaluate the potential risk of no security versus the cost of
implementing and administering security, and then decide.
If you decide to implement security, thoroughly familiarize yourself
with the process by reviewing the Microsoft Access help file.
To create security, the steps are-
Create a new workgroup.
Attach to your new workgroup file using the Microsoft Access
Workgroup Administrator.
Start Microsoft Access.
Create new users and passwords.
Attach your DBA tables.
For each new user created in 4, assign Read Only permissions for each
DBA table attached.
For at least one user created in 4, assign Administrative permissions
for each DBA table attached.
Remove all permissions for each DBA attached table from the Admins
and Users group and from the Admin and User users.
Back to top
Download to Trouble Shooting.rtf to trouble shoot ODBC
connectivity problems
Back to top
Having problems connecting to your data source?
Call us for technical assistance on a pay per incidence basis and we
will work through your problems until you have successfully connected to your DBA data
source.
Telephone
586-412-2400
FAX
586-412-2405
Postal address
42621 Garfield Road, Suite 106, Clinton Twp., MI 48038
Electronic mail
grandazzo@mwaccounting.com
|
