 |
|
|
How
to connect to Oracle 10g on a Unix-based server?
The
steps to connect to an Oracle database on a Unix-based (or
Solaris-based) server are the same as connecting to an Oracle
database on a Windows server. First, you must create a Service
Name on the client for the remote Oracle database:
-
On
the client PC, start the Net Manager program from
Oracle. To start this program, press
Start->Programs->Oracle_<Home>
->Configuration and Migration Tools->Net Manager.
-
In
Net Manager, create a Service Name for the Oracle database
service on the Unix-based server. You will need to know the
host name of the server and the SID of the Oracle database
in question.
-
Using
Net Manager, you can test the connection from the client to
the database service.
Next,
you must create a DSN entry for the ODBC driver on the client.
To do this:
-
In
CardFocus, click on Network Database in the database
conection dialog and click on the Manage DSN Datasources button
to invoke the Windows ODBC Administrator.
-
Click
on the System DSN tab and then the Add button
to create a new System DSN entry.
-
Select
the Oracle ODBC driver, assign a name to this DSN entry and
select the TNS Service Name that you created using the Net
Manager (see above).
-
On
the Workarounds tab, ensure the Force SQL_WCHAR
Support option is selected.
Before
connecting to the Oracle database, ensure that Client-side
database cursors are being used. To do this, check that Client-side
cursors is selected on the Connection tab in Database
Options in CardFocus.
Finally,
in the Network Database dialog in CardFocus, select your new DSN
entry, enter a database Username and Password and click the Open
button to connect to the database.
Back
to top |
|
Where
does Oracle Objects for OLE (OO4O) need to be installed?
If
you are using Oracle Objects for OLE (OO4O) for connection to an
Oracle database, then Oracle Objects for OLE must be installed
on the samce PC as CardFocus.
To install Oracle Objects for OLE, you will need to download the
version of the OO4O installer that matches your installation of
Oracle.
You can download OO4O installation packages from the
Oracle website at
http://www.oracle.com/technology/software/tech/windows/ole/index.html
If
OO4O is not installed, then you will get the error "ActiveX
Component Can't Create Object" when CardFocus attempts an
OO4O connection to the Oracle database.
Back
to top |
|
Which
version of Oracle Objects for OLE (OO4O) should be used?
CardFocus
is built against Oracle Objects for OLE (OO4O) for Oracle 10g.
So this is the version of OO4O that should be installed on the
same PC as CardFocus.
CardFocus can access an Oracle8i, Oracle9i or Oracle10g database
through a local connection or a network using the Net client.
Oracle Net will need to be installed when accessing an Oracle
database through a network.
Back
to top |
|
Storing
photos in an Oracle database?
It
is recommended to use a LONG RAW field type rather than a BLOB
to store a photo image in an Oracle database table. A LONG RAW
can hold up to 4GB of binary data.
Back
to top |
|
How
to connect to SIMS schools MIS from CardFocus?
SIMS
is a management information system for schools. CardFocus
can connect directly to the SIMS database, enabling access to
data that has already been collected in SIMS.
The
steps to connect to the SIMS database are the same as connecting
to a Microsoft SQL Server database as SIMS is based on MS SQL
Server.
First, you must create a user for the database on the SIMS
server. On the server, start the Enterprise Manager program from
Microsoft. To start this program, press
Start->Programs->Microsoft SQL Server->Enterprise
Manager
In Enterprise Manager, create a user for the SIMS server. On the
left of the Enterprise Manager screen, expand the Microsoft SQL
Servers icon. Click on Databases and then on the SIMS database
to expand this database entry. Click on the Users icon and then
on the right-hand side of the Enterprise Manager screen,
right-click and select New Database User. Follow the steps to
assign a user name and password for your new user.
While using Enterprise Manager, make a note of the new user
name, password, the SIMS Server name (the SQL Server group
entry) and the database name in this SQL Server (probably SIMS
or something similar).
In CardFocus (either on the same server PC or on a PC networked
to the server PC), click on the File->New menu to create a
new blank card. Click on the Database->Connect menu to open
the Data Source dialog and create a connection to a database for
this card.
In the Data Source dialog, click on Network Database, to open
the Network Database dialog. Here, choose the database type to
be SQL Server, enter the server name, database name (Data
Source), user name and password as noted in Enterprise Manager
and press the Open button. Finally, select the table you wish to
use for managing your identity cards.
After connecting to a table, save your new ID card file. Next
time you open the card file, it will automatically open the
connection to the database.
Back
to top |
|
File
scrrun.dll causing an error during installation?
During
installation, some Windows 2000 users (and occasional XP users)
may get the error message 'Error 1931. The Windows Installer
service cannot update the system file C:\<WINDOWS
PATH>\System32\scrrun.dll because the file is protected by
Windows......' as shown below;
If this message is shown during installation, click the 'Ok'
button to continue. The message is shown when a system file that
is needed by CardFocus, is already installed on the target
computer. Clicking 'Ok' skips the attempted installation of this
file and after installation of CardFocus is complete, you should
find the the application works as expected.
Back
to top |
|
Run-time
error 713?
This
error can occur when CardFocus is installed on a Win NT/2000 PC
that needs Admin authority to install software or certain DLL's
were installed by other programs and not registered during the
install process. Here is how to fix the problem after installing
CardFocus. If you are running Windows95/98 you should download regsvr32.exe
from our site and save it in the root directory of your C:
drive.
1.
Find where the DLL is located that needs to be registered. To do
that you run Regedit from Start/Run. Regedit it what you use to
view and make changes to the System Registry. To find the DLL
use the Edit/Find command and type in the address of the DLL
that appears in parenthesis after CLSID in the error message The
number will look like this
(000000010-0000-0010-8000-00AA006D2EA4) but maybe a different
set of values. When you find the folder it will be highlighted
with this address next to it as it's name.
2. Now double-click on the folder and two other folders will
display. Double-click on the folder InprocServer32. To the right
you will see under the Data column the name and location of the
DLL with this class number. Now that we know which DLL it is and
where it is located you can register it.
3. From the DOS prompt enter the full path to get to the DLL
that was displayed from Regedit. Then type Path C:\ so
DOS will be able to find regsvr32.exe.
4. Now you will unregister the DLL. For Win NT/2000 type C:\WINNT\System32\Regsvr32
/u NAMEOF.dll For Windows 95/98 type C:Regsvr32 /u
NAMEOF.dll .
5. Next you register the DLL again. For Win NT/2000 type C:\WINNT\System32\Regsvr32
NAMEOF.dll For Windows 95/98 type C:Regsvr32 NAMEOF.dll
.
6. Quit out of DOS and reinstall CardFocus. That should take
care of the problem unless there is another DLL that needs to be
registered. If so, go through Step1-5 again to register another
DLL.
Note,
to confirm Admin permission level see the following before
installing:
Steps
to confirm your permission level with Windows NT 4.0:
-
Click
on the Start button > Programs > Administrative Tools
(Common) > User Manager
-
Double
click user name
-
Click
on the groups tab
-
The
dialogue box on the bottom left hand side must indicate that
you are a member of "Administrator" groups, if
you are not please contact your local IT department
-
If
you receive an error message stating," The following
error occurred accessing the properties of the user, access
is denied, the user properties can not be edited or viewed
at this time", this confirms you do not have
Administrator privileges.
Steps
to confirm your permission level with Windows 2000 Professional:
-
Click
on the Start button > Settings > Control Panel >
Users and Passwords
-
Select
your user name
-
Click
on the properties tab
-
Under
the group membership tab your permissions level will be
identified if it does not indicate that you are a member
of the Administrator group please contact your local IT
department.
-
If
you receive an error message stating "you must be a
member of the Administrator group or this computer to open
Users and Passwords control panel" when you try to view
the properties of the user account, this confirms that you
are not a member of the Administrator group
Steps
to confirm your permission level with Windows XP:
-
Click
on the Start button > Control Panel > User Account
-
Are
you limited to only actions that affect your personal user
account and no others such as "Change your account
password" or "Change your picture"?
If you do NOT see choices labeled "Create a new
account" or "Edit an account", then it does
not appear that your current user account has ADMINISTRATIVE
privileges on the Windows XP PC.
Back
to top |
|
Networked
drive issue?
Some
configurations will require connection of a card to a remote
database on a mapped networked drive. For this to work properly,
ensure that the user has full access to the networked drive and
to the database on that drive, i.e. Admin privileges to the
drive if necessary. Otherwise, errors will occur when attempting
to connect to the database, e.g. DB Build Error.
Back
to top |
|
Error
1904 - Failed to register during installation?
Some
Windows users are encountering a Failed to Register error
message during the CD-Rom installation of CardFocus.
We
are encouraging these users to visit the official Microsoft
website to download and install a file that should correct this
installation problem.
Steps
to install DCOM:
-
Click
on the appropriate link below to access this website:
Windows 95: http://www.microsoft.com/com/dcom/dcom95/download.asp
Windows 98: http://www.microsoft.com/com/dcom/dcom98/download.asp
This will open a new browser window.
-
Click
on the link provided at this page for "DCOM9x for
Windows 9x".
-
Save
this file to disk, and when possible save this file to your
"Desktop".
-
Once
the download is complete, close all applications and run
this file by double-clicking on the icon labeled DCOM9x.EXE
-
Once
the file has been run, reboot the computer.
-
Once
the computer has rebooted, try the installation following
the supplied documentation.
-
If
the error occurs again click ignore and finish the
installation. Restart the program, it should work normally.
-
If
this, or other problems, persist then contact Sabadille
Support:
CLICK
TO REPORT ISSUE
Back
to top |
|
Missing
run-time files on older systems?
It
is sometimes wrong to assume that you have all the necessary
run-time files to enable you to install and run new programs. In
particular, if you don't download very often and you don't use a
lot of software other than what came with your computer - you
may need an additional support file here and there. Microsoft
releases new "Run-time" files every now and then. They
allow software developers to make use of the latest technology
when creating new software. In order for you to use these
programs, you need to update your Windows system with these
files. Our current software products require the VB6
Runtimes.
VBRun60.exe
Installs Visual Basic 6.0 Run-Time Files
This package includes: ASycFilt.dll, ComCat.dll, MSVBVM60.dll,
OLEAut32.dll, OLEPro32.dll, STDOLE2.tlb, ADVPack.dll,
W95Inf16.dll, W95Inf32.dll, VBRun60.inf.
Back
to top |
|
Database
search facility producing errors?
If
the database search facility in CardFocus is producing errors,
then ensure that your database table has a primary key. If there
is no primary key on the table, then it is advisable to create
one.
Back
to top |
|
SQL
Server - error -2147467259 Key column information is
insufficient or incorrect. Too many rows were affected by
update.
This
is an SQL-Server problem that trips many people up. SQL is built
around set concepts, so it has no trouble inserting any number
of identical records, but, if you ever want to update any of
these identical records, you are in trouble.
The problem is that SQL Server (and other SQL based servers) do
not keep track of record numbers, so there is no inherent unique
identifier for each record. If you intend to update some record,
and you intend to do this with any SQL based server, then you
must be certain that the table you want to update has a unique
row identifier AND that you have provided that information
during the row updates. Otherwise the SQL Server logic returns
the error above, essentially getting confused about which record
you want the SQL Server to update?
There are a couple of ways around this:
-
Add
an auto-incrementing integer column ('int' data type,
non-null with 'identity seed' 1 and 'identity increment' 1).
You never change the value of such fields as they are set
during INSERT commands.
-
You
can compute some unique key and insert that with every
INSERT command.
Back
to top |
|
Database
password issue on Windows 2000/XP?
If
you are prompted for a database password when connecting to a
database on Windows 2000/XP for which no password was set, then
there is a problem with your Microsoft Data Access Components (MDAC)
installation.
We are encouraging users with this issue to visit the official
Microsoft website to download and (re)install MDAC 2.8 on
Windows 2000 plus the latest MDAC service pack.
Steps
to install MDAC:
-
Click
on the appropriate link below to access this website:
http://www.microsoft.com/data/
This will open a new browser window.
-
Click
on the link provided at this page for MDAC 2.8 (or the
latest MDAC update for XP users).
-
Save
this file to disk.
-
Once
the download is complete, close all applications and run
this file by double-clicking its icon.
-
Once
the file has been run, reboot the computer.
-
Once
the computer has rebooted, try again to connect to your
database.
-
If
this, or other problems, persist then contact Sabadille
Support:
CLICK
TO REPORT ISSUE
Back
to top |
|
Pictures
stored in MS Access - 'Package' Storage?
If
you store images in an OLE Object field in MS Access using an
Access form, then CardFocus will most likely not be able to read
the image. CardFocus requires that images be stored in the
database as binary long objects (BLOBs).
The OLE 'Package' storage in MS Access is just that - it isn't
storing the image, but a complete OLE reference to the picture
AND the application responsible for it. This leads to an amazing
bloat in the database. The data type is OLE, which is why you
cannot just view the data in an image control (or in CardFocus)
- MS Access has to activate the application responsible for
processing the OLE 'Package' storage.
Broadly speaking, what this means is that if CardFocus were to
try to use 'Package' OLE for displaying images, it would be
"at the mercy" of a number of unobvious property
settings and, even worse, "at the mercy" of whatever
automation-enabled image-processing software is associated with
the image file type on the machine where the picture was
captured to the database (which, of course, may be significantly
different to the one associated with that file type on the
current machine).
So, just like other products in its category, CardFocus stores
images in the database as binary long objects (BLOBs). By this
mechanism, only the pure image data is stored and therefore the
image type must be manually seletced in the database options
window in CardFocus.
Back
to top |
|
Error
-2147217887 - Multiple-step OLE DB operation?
The
error number is -2147217887 and the message is "multiple
step OLE DB operation generated errors." There are a number
of reasons why you might get this error message when trying to
update a record in a MS Access database. The first thing to
check, if the table contains many records, is whether the table
has a unique primary key.
Very often, the MS Access database logic returns the error above
when it gets confused about which record you want to update?
The solution in this instance is to add a unique primary key to
the table. If this problem persists after the addition of a
primary key, then contact Sabadille Support:
CLICK
TO REPORT ISSUE
Back
to top |
|
Error
-2147467259 - Key column information is insufficient?
The
error number is -2147467259 and the message is "key column
information is insufficient or incorrect, too many rows were
affected by update." This message usually indicates that
the table lacks a unique primary key. MS Access is confused
about which record you want to update.
The solution in this instance is to add a unique primary key to
the table. If this problem persists after the addition of a
primary key, then contact Sabadille Support:
CLICK
TO REPORT ISSUE
Back
to top |
|
Unable
to bind to field or data member?
If
you store images in an OLE Object field in MS Access (internal
images), then CardFocus binds to this field when opening the
database table. If the field contains image data that is somehow
corrupted, then CardFocus will not be able to bind to the field
and will produce the error message "unable to bind to field
or data member."
The solution is to delete the contents of the field in MS
Access. It should suffice to delete the contents of the field in
the first record of the table only.
Back
to top |
|
Duplicate
value errors after compacting Access database?
If
your data source is a Microsoft Access database that you compact
from time to time and you use a primary key field of type
autonumber, then after compacting you might get an error when
creating new records in CardFocus. The error message is the
following:
"The changes you requested to the table were not successful
because they would create duplicate values in the index, primary
key and relationship changing the data in the field/fields that
contain duplicate data, remove the index or redefine the index
to permit duplicate entries or try again."
The cause of this problem is that, through compacting the
database, the autonumbering mechanism gets corrupted. This is a
known Microsoft bug, see the Microsoft knowledgebase article
257408.
The solution is to install the latest service pack for the
Microsoft Jet 4.0 Database Engine. The latest service packs can
be found at
http://support.microsoft.com/default.aspx?kbid=239114#9
Back
to top |
|
Support
for international (non-Western) language text?
To
properly display some international (non-Western) text in
CardFocus, you need to select the GUI font and character set in
the Language Font configuration menu.
Character sets, simply said, are display mappings between byte
or byte values and the actual character glyphs seen on the
screen or printer. The "Western" character set is the
default for most Windows installations and includes, basically,
North and South America and parts of Western Europe.
However, for countries and languages that are not considered
Western, an appropriate character set must be selected,
otherwise characters in these languages will not be displayed
correctly in CardFocus. There's provisions for Greek, Turkish,
Central European, Russian (Cyrillic), Hebrew, Arabic, Baltic
states, Chinese, Japanese, Korean, etc.
A further complication in choosing character sets is that not
every font supports every character set. Arial seems to support
the most character sets, as does Times New Roman, Courier New,
and Tahoma, but it is a case of trial and error to discover if
the font you wish to use for the GUI supports your chosen
character set.
Back
to top |
|
Error
-2147467259 - [Microsoft][ODBC Microsoft Access Driver] General
error unable to open registry key Temporary (volatile) Jet DSN
This
error generally means there is a system permissions problem. For
example, it may occur if you install CardFocus as Administrator,
and non-Administrator users try to use the program. Here are
some steps to take to try to resolve this issue:
1. CardFocus needs "write" permission to the directory
where the Access database resides. So, set permissions for the
user account so that the user has write permission to the
database directory and to the Windows TEMP directory.
2. Give the same account write permission in MS Access itself
(Tools -> Security menu). These permissions can be reset by
MS Access if you compact and repair the database so keep in mind
to refresh this permission as necessary.
Back
to top |
|
Using
MyODBC for MySQL - error 545 - unable to bind?
This
error can occur when you try to connect to a MySQL data source
using MyODBC. The error is due to the presence of a DATETIME
field with an invalid default value in the MySQL table. To
workaround this problem, ensure that all DATETIME fields
in your MySQL table have the default value NULL (and not a
string of zeros as is standard in MySQL) and can accept NULL
values.
Back
to top |
|
Error
1706. Setup cannot find the required files?
After
you have installed CardFocus and you try to start the CardFocus
software, you might get this error. It is not a CardFocus error,
but rather a Windows error and is related to your Microsoft
Office installation. For instructions on how to combat this
error, see the Microsoft support page:
http://support.microsoft.com/kb/297834
Back
to top |
|
Word-wrap
is often not the same on screen as the printed card?
When
using multi-line word-wrapped static text on cards, the
word-wrapping as viewed on the screen in CardFocus is sometimes
not the same as what is printed on the card by the printer. On
the printed card, words can appear on different lines and have
ends chopped off.
The solution is, when working with multi-line word-wrapped text,
preview the card at 100% Zoom level in CardFocus. This gives
true WYSIWYG preview, i.e. multi-line word-wrapped text that you
see on the screen is the same as what is printed on the card.
The cause of the problem is that text Fonts don't zoom well,
e.g. if you have a font-size 13 and you choose card zoom level
of 150% in CardFocus, then you get a font-size of 19.5. Windows
rounds this size up/down to the next available font size for
that particular font, resulting in larger text in the same size
text box which may cause the word-wrap to behave differently.
Back
to top |
|
How
to connect my cards to a MS Visual FoxPro file?
With
a few mouse clicks you can connect and use the data in a MS
Visual FoxPro file (.DBF) directly on your cards. Here's how:
-
Open:
Start -> Control Panel -> Administrative Tools ->
Data Sources (ODBC).
-
Click
on System DSN, then on the 'Add' button and select
'Microsoft Visual FoxPro Driver'.
-
Enter
a name to describe this entry, e.g. 'MyFoxPro', then click
the Browse button to navigate to the folder where your
FoxPro files 'myfoxpro.DBF' and 'myfoxpro.FTP' are located.
-
Select
the 'Free Table Directory' option and click 'OK' to finish.
Next,
in CardFocus:
-
Select
the menu File -> New and click on 'Connect'.
-
Click
on the 'Network Database' button and then double-click on
your DSN entry (e.g. 'MyFoxPro') in the list with the
heading 'Click to select DSN Datasource'.
-
Click
the 'Open' button and then select a FoxPro table and click
on the 'OK' button.
-
Select
the menu File -> Save As to save your card so that the
next time you open the card, the database connection will be
established automatically.
Now
you can draw objects on the card and select 'Database' as the
source of these objects.
Back
to top |
|
Screen
ghosting effect experienced using CardFocus GUI?
For
ease of use, CardFocus offers an advanced non-standard Windows
graphical user interface (GUI). In some installations, a
ghosting effect can be experienced when using this GUI, whereby
buttons do not appear to be placed where they are expected on
the screen, but rather are placed at an offset.
To
correct this problem:
- Open:
Start -> Control Panel -> Display.
- Switch
to the 'Settings' tab and click on the 'Advanced' button.
- Ensure
that the DPI setting is set to 'Normal Size', e.g. 96 DPI.
For Windows 7:
- Open: Start -> Control Panel -> Appearance and Personalization -> Display.
- Here you will see a number of possible settings for the DPI
- Smaller - 100% = 96 DPI (Pixels/Dots Per Inch)
- Medium - 125% = 120 DPI (Pixels/Dots Per Inch)
- Larger - 150% = 144 DPI (Pixels/Dots Per Inch)
- Ensure
that the DPI setting is set to 'Smaller - 100%', e.g. 96 DPI.
If you have to change the DPI settings, ensure to restart Windows for the change to take effect.
Back
to top |
|
Cannot
add new records to Access database because of duplicate
autonumber values?
From
time to time in MS Access, autonumbering can become corrupt and
it becomes impossible to add new records because autonumbering
produces values that duplicate existing values. This problem is
usually corrected by selecting Tools->Database
Utilities->Compact and Repair in the MS Access program
for the database in question.
However, sometimes the problem is due to a bug in a Windows
component called the Jet engine and Compact and Repair
cannot solve it. The solution then is to apply the latest Jet
Service Pack to your operating system - for more details, see
http://support.microsoft.com/kb/q257408/
The
Jet Service Pack can be downloaded from the Microsoft website:
http://support.microsoft.com/kb/239114/
Alternatively,
on the CardFocus installation CD there is a folder called MS
Jet Engine and this folder contains Jet Service Packs for
many of the Windows operating systems.
Back
to top |
|
Could
not open/create registry section - check registry permissions.
This
is a problem with the permissions of the current Windows user
for updating the system registry. It shows up as "Run-Time
error -2147219499(800407d5)".
This
often occurs in corporate settings where only the system
administrator is allowed to install new software. To correct
this there are 2 solutions.
The
first is to change the registry permissions for the current
Windows user. To do this, login to Windows as system
administrator and do the following:
-
Select
"Run..." from the Start menu
-
Type
"regedit" (without the quote marks) and press
"OK". Note, on Windows 2000, you should use
"regedt32.exe" instead of "regedit.exe".
-
You
will see a "tree". Press the "+" next to
"HKEY_LOCAL_MACHINE".
-
Right-click
on "SOFTWARE" and select "Permissions"
from the menu that appears.
-
Scroll
down the list to "Users" and select it by tapping
on it once.
-
Check
the box next to "Full control" in the
"Allow" column.
-
Press
"OK" to close the dialog box, and then close the
Regedit program.
-
To
be on the safe side you may want to reboot your computer,
and then run CardFocus again.
The
second solution is to use user-based registry settings as
opposed to machine-based registry settings. To do this, in
CardFocus use the Configuration->Registry Settings menu to
change from using machine-based settings to user-based settings.
Back
to top |
|
Error
482 when selecting a printer?
Error
482 encompasses numerous printer errors, including some that are
not covered in the documentation. We found that one of our
customers could solve this by changing the printer’s settings
in Windows to the correct port.
Back to top |
|
How
to mask a barcode?
Barcode
masking is the technique of applying a dark box over a barcode
during printing so as to make it impossible to photocopy the
barcode. To the naked eye and to a photocopy machine, all that
is seen is a dark box. To a barcode reader, the barcode can be
deciphered from the dark box.
How
this works relies on the difference between how the barcode is
printed and how the surrounding box is printed; the barcode is
printed in resin black and the box in composite black. A barcode
reader can distinguish the resin black from the surrounding
composite colour and therefore read the barcode.
Barcodes
generated using the barcode tool are sent to the printer as
bitmap images, so depending on the printer driver, may or may
not be printed in resin black.
To
ensure that a barcode is printed in resin black, it is
recommended to acquire the barcode font and create the barcode
as a text object. This leaves no doubt that the barcode will be
printed in resin black.
The
box used to mask the barcode can be black or dark grey,
depending on preference. This box should be printed in composite
black.
Back to top |
|
Error 3219 Operation is not allowed in this context
on Windows 2000?
If
you encounter error "3219 Operation is not allowed in this
context" when checking visitors IN/OUT on a W2K
system, then
there is probably a problem with your Microsoft Data Access Components
(MDAC)
installation.
We are encouraging users with this issue to visit the official
Microsoft website to download and (re)install MDAC 2.8 on
Windows 2000, plus the latest MDAC service pack.
Steps
to install MDAC:
-
Click
on the appropriate link below to access this website:
http://www.microsoft.com/data/
This will open a new browser window.
-
Click
on the link provided at this page for MDAC 2.8 (or the
latest MDAC update for XP users).
-
Save
this file to disk.
-
Once
the download is complete, close all applications and run
this file by double-clicking its icon.
-
Once
the file has been run, reboot the computer.
-
Once
the computer has rebooted, try again to connect to your
database.
-
If
this, or other problems, persist then contact Sabadille
Support:
CLICK
TO REPORT ISSUE
Back to top |
| |
Omnikey
5121 Mifare encoder in Fargo HDP5000 printer not responding?
If you
preparing to encode Mifare cards on the Fargo HDP5000 with
the embedded Omnikey 5121 Reader Board, then you might see an
error such as the following: "OMNIKEY: The smart card cannot be accessed because of other connections outstanding"
Most likely this error is thrown because there are other reader
devices installed and the Microsoft Smart Card Resource
service has difficulty with connections.
To get around this problem, stop the Microsoft Smart Card
Resource service and restart it. By stopping the service, othere
devices will be disconnected.
Stop
and restart the Microsoft Smart Card Resource Service
-
Open a command
prompt as follows: click Start, point to All programs, point to Accessories, and then click Command Prompt.
Alternatively, click Start, Execute and type 'cmd'.
-
Stop
the Smart Card Resource service by typing 'net stop
scardsvr' at the prommpt.
-
Retstart
the Smart Card Resource service by typing 'net start
scardsvr'.
Back to top |
| |
MS Access error -2147217873 ODBC Microsoft Access Driver, duplicate values in the index, primary key or relationship?
This problem occurs when a MS Access database is corrupted and starts assigning negatives or duplicate values in an AutoNumber field. In Access 2000 and later, an AutoNumber field may begin assigning extreme values, negatives, and even duplicates. The attempt to assign a duplicate fails if the field is a primary key, making it impossible to save new records in an affected table.
The solution to this problem is to fix the Autonumber-ing in the Access database and apply JET 4 Service Pack (7 or later) to prevent the problem recurring.
To apply JET 4 Service Pack, select the service pack for your version of Windows form the JET SP download page and follow the instructions to install. The download page can be found at
http://support.microsoft.com/?id=239114
To fix the problem in the current database, reset the AutoNumber seed as follows:
You may be able to solve the problem with a compact/repair. In Access 2007 use Office Button -> Manage. In earlier versions use Tools -> Database Utilities -> Compact & Repair
Alternatively, the code below checks all tables in your database, and offers to fix any where the seed of the AutoNumber is less than zero or below the existing values. The function returns the number of tables that were changed - zero if none had the problem. It does not alter the values of any duplicate values in the AutoNumber field.
It works only with Access 2000 or later, but then earlier versions do not have this problem.
Instructions
- Make a backup of your database.
- In the Access application window (the Nav Pane in Access 2007), choose the Modules tab, and click New. Access opens a new code window.
- Copy the function below, and paste into the code window.
- Choose References from the Tools menu, and check the box beside: "Microsoft ADO Ext. 2.x for DDL and Security".
- From the Debug menu, choose Compile to check there are no problems.
- Press Ctrl+G to open the Immediate Window.
- Enter: ? AutoNumFix()
Here is the code:
Function AutoNumFix() As Long
'Purpose: Find and optionally fix tables in current project where
' Autonumber is negative or below actual values.
'Return: Number of tables where seed was reset.
'Reply to dialog: Yes = change table. No = skip table. Cancel = quit searching.
'Note: Requires reference to Microsoft ADO Ext. library.
Dim cat As New ADOX.Catalog 'Catalog of current project.
Dim tbl As ADOX.Table 'Each table.
Dim col As ADOX.Column 'Each field
Dim varMaxID As Variant 'Highest existing field value.
Dim lngOldSeed As Long 'Seed found.
Dim lngNewSeed As Long 'Seed after change.
Dim strTable As String 'Name of table.
Dim strMsg As String 'MsgBox message.
Dim lngAnswer As Long 'Response to MsgBox.
Dim lngKt As Long 'Count of changes.
Set cat.ActiveConnection = CurrentProject.Connection
'Loop through all tables.
For Each tbl In cat.Tables
lngAnswer = 0&
If tbl.Type = "TABLE" Then 'Not views.
strTable = tbl.Name 'Not system/temp tables.
If Left(strTable, 4) <> "Msys" And Left(strTable, 1) <> "~" Then
'Find the AutoNumber column.
For Each col In tbl.Columns
If col.Properties("Autoincrement") Then
If col.Type = adInteger Then
'Is seed negative or below existing values?
lngOldSeed = col.Properties("Seed")
varMaxID = DMax("[" & col.Name & "]", "[" & strTable & "]")
If lngOldSeed < 0& Or lngOldSeed <= varMaxID Then
'Offer the next available value above 0.
lngNewSeed = Nz(varMaxID, 0) + 1&
If lngNewSeed < 1& Then
lngNewSeed = 1&
End If
'Get confirmation before changing this table.
strMsg = "Table:" & vbTab & strTable & vbCrLf & _
"Field:" & vbTab & col.Name & vbCrLf & _
"Max: " & vbTab & varMaxID & vbCrLf & _
"Seed: " & vbTab & col.Properties("Seed") & _
vbCrLf & vbCrLf & "Reset seed to " & lngNewSeed & "?"
lngAnswer = MsgBox(strMsg, vbYesNoCancel + vbQuestion, _
"Alter the AutoNumber for this table?")
If lngAnswer = vbYes Then 'Set the value.
col.Properties("Seed") = lngNewSeed
lngKt = lngKt + 1&
'Write a trail in the Immediate Window.
Debug.Print strTable, col.Name, lngOldSeed, " => " & lngNewSeed
End If
End If
End If
Exit For 'Table can have only one AutoNumber.
End If
Next 'Next column
End If
End If
'If the user chose Cancel, no more tables.
If lngAnswer = vbCancel Then
Exit For
End If
Next 'Next table.
'Clean up
Set col = Nothing
Set tbl = Nothing
Set cat = Nothing
AutoNumFix = lngKt
End Function
Back to top |
| |
For DESFire, cannot conenct to CrazyWriter encoder?
The software supports DESFire EV1. For this, the Springcard CrazyWriter device has to be in PC/SC mode, and not legacy mode, otherwise the connection attempt to the DESFire card will fail. To put the encoder in PC/SC mode:
- Step 1
Connect the CrazyWriter (currently in Legacy mode) to your computer, and follow the driver installation wizards until the device has been installed.
- Step 2
Open the Explorer, and navigate to the place where the Quickstart for CrazyWriter PC/SC has been installed. Typically, this is in folder c:\Program Files\SpringCard\SDD4C0.
Launch the program named csb6_go_pcsc.exe. This is a command-line utility. When prompted, enter "YES" to confirm you are ready to « permanently » transform your Legacy CrazyWriter into a PC/SC CrazyWriter.
Once the device has been programmed, press any key to close the command-line window.
Unplug the CrazyWriter from its USB connector (on devices with an external power source, such as a CrazyWriter mounted in some printers, you must switch OFF the power source as well).
Wait a few seconds, and plug the CrazyWriter again (switch ON the power source in case there's one).
Windows now loads the PC/SC Driver.
Back to top |
|
