> as appealing for most people. One of the changes that I
> intend to make
> is to allow the code to be smart enough to determine whether the user
> has insert/update/delete permissions (verses just select) in which
> case, it will link them to the master copy instead of a slave
> for read
> only access.
>
> That process has also allowed me to work around a couple of other
> issues with ODBC that I do not care for. Another issue is that the
> user name is stored in the registry and the MS Access user
> name is not
> used. I have code in the startup routines that rewrite the registry
> keys to use the username of my choice (Currentuser()). The ODBC
> password is stored in plain text in the registry. The shortcomings
> there is obvious. So, I am rewriting the password as well. An
> interesting thing to note is that ODBC only reads the registry keys
> when relinking the tables, So I write the registry keys, delete the
> links, relink the tables, and then re-write the registry keys with
> bogus data. Anyone reading the registry keys won't recover the
> username and password. One other side note is the password
> that I use
> is not the password that the user gives me. I hash their
> password, and
> give the hash to MySQL as a password. That prevents the users from
> using anything but my application to access the tables. Most of the
> business logic for our application is in the front end. It would be
> unfortunate if someone was to side step that and edit the tables
> without any validation or referential integrity.
I would be interested in this code you are talking about. I not sure I
understand how exactly you are doing this. Are you doing VB/macros? To
detect insert/update/delete would be the best route I would think, instead
of always deleting the linked tables each time the database is loaded. What
would happen if someone tries to modify the schema of table through M$
Access? Would it not screw things up or I assume at the least limit your
control.
> -----Original Message-----
> From: mysql-digest-help [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 24, 2001 6:08 PM
> To: venu; turner; mysql
> Cc: adouglas
> Subject: RE: RE: Info Needed to Promote MySQL!!
>
>
> > As a quick note, I tried the same with MS SQL Server through
> > its latest ODBC
> > driver by adding the new column, and I couldn't see any
> changes in the
> > linked tables from Access 2002.
> >
> > So it shows clearly that, its some thing related to MS
> > Access, not with the
> > driver. It might be a bug from Access or there might be some
> > setting that we
> > need to do it, inorder to see the changes to the table structure.
>
> So is this going to be looked into on how to resolve this issue or is
> it not
> fix able unless M$ does something?
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
