Re: Issues with linking encrypted tables

Liz McGuire wrote:
> Just a note so your expectations don't get too high...
Ah, but you've been very helpful! I won't always *expect* such great
help, but I do appreciate it!
>
> > If it is Paradox, how can I tell what version of Paradox?
>
> On this page - http://info.borland.com/devsupport/bde/utilities.html -
> there's a utility called "Paradox table alter"
>
> There's also a "Table Interrogator" utility on this page which gives you
> TONS of info about a Paradox table - can be very useful

Okay, thanks to Liz, I have now verified that this is a Paradox
database, version 7.

> question - did they give you the password or did you go get it?

We use the manufacturer's hardware and their software is included. They
don't give out the password to the actual database: instead they
provide a utility that exports the 'working' database to a 'read-only'
version and provide the password to that. Read-only is fine as I just
need to *display* the prox card data along with data from the employee
ID database which is SQL.

> Now I'm really curious, how, exactly, are you getting Access to open the
> database if not via ODBC? OK, just tried this in Access 2003 - it'll open
> level 7 tables with no problem... I expect it's making an ODBC connection
> on the fly. It's read-only though. (So are level 5 tables - maybe it does
> some kind of quick conversion and gives you a read-only view - no clue.)

You're right, I can link (or import) the Paradox tables to my Access
2002 frontend without any ODBC connection. I've learned that if I could
use ODBC to connect to the Paradox database, I could supply the needed
password via code behind the scenes. I'm sure there are methods other
than ODBC to refresh linked encrypted tables but my knowledge is
lacking!

> DataDirect / Intersolv - it's not cheap. Otherwise, buy a copy of Paradox
> (v8 came with the Intersolv driver, not sure about 9, pretty sure 10+ did
> NOT include the ODBC driver).

Okay, so I've done a search for an ODBC driver for Paradox 7. I looked
the websites you've offered, but don't see any prices? "Not cheap"
isn't encouraging, but my supervisor might be willing. I see some free
trial versions so I could test the connection. They're tempting...

Perhaps someone out there has a code snippet to refresh the connection
to the encrypted Paradox database without using ODBC? Decrypting the
database is not an option.

Thank you again for your help! I feel like I'm getting somewhere (and
learning!). Fortunately the boss is gone for a couple of weeks.
Hopefully I'll have some good progress by then. Jill Elaine

.

Relevant Pages

  • Re: Issues with linking encrypted tables
    ... Paradox the application to access Paradox the table format natively. ... The prox card database ... > If I knew what version of Paradox, I might be able to create an ODBC ...
    (comp.databases.paradox)
  • RE: Unable connect to sybase database
    ... Turn it off if you are on a corporate network. ... Recreate the odbc connection and see if it works. ... Or else you can go for OLE DB Providers to connect to the database. ... OLE DB is an advanced protocol and much better than ODBC. ...
    (microsoft.public.windowsxp.perform_maintain)
  • RE: ODBC--Connection to Database failed
    ... Have you defined on your ODBC connection the database you working with? ... > this .mdb file, and runs a query, and it works for him. ...
    (microsoft.public.access.gettingstarted)
  • Re: CRecordset::Open and MySQL (ODBC) - nOpenType ?
    ... I started a new application through the steps of the assistant with ODBC ... This means the DSN would be shown but not accepted. ... Now I think that my version of VS2005 isn't able to access a MySQL database ... the ODBC connection that is forcing the forward-only. ...
    (microsoft.public.vc.database)
  • ODBC connection string for make-table query (Access 97)
    ... My database makes an ODBC connection ... ODBC Linked tables. ... I have seen examples for pass-through queries, where on the query ...
    (microsoft.public.access.queries)