Skip to main content

Whithin the Maximizer database there is a AMGR_Client view. It contains all the info from the AMGR_Client_Tbl table. I would like to do some searching on this view with Pervasive ODBC. When I search it does not return all the values as queried.

It seems that Maximizer adds spaces after values. When I run an update command on the database to remove the spaces after the values, it works 100%, ie update amgr_client_tbl set record_type=record_type or any field for that matter.

According to the Maximizer website, the Pervasive ODBC can be run to get information out of the database.

Is this correct?
Original Post
If you are planning to query your Maximizer Database from the backend on a regular basis, I would suggest that you move to the SQL version of Maximizer Enterprise. SQL has many tools to suite all levels of experience when querying, also with Microsoft SQL you can make your own triggers... etc. I find Pervasvie to be slow and akward when querying the DB.

P.S. I have not experienced any spaces at the end of any values being added in by the program. Are you sure your users are not typing in the spaces when adding contacts?

Add Reply

Post
LEGAL INFO
CONTACT US
Copyright 2007-2018 Advoco Solutions Ltd. All Rights Reserved.
×
×
×
×
Link copied to your clipboard.
×