-
MySQL Question
I am VERY VERY new to this MySQL
stuff.
I have converted from Access to MySQL
and I have all the tables indexed,
the security for the admins to be
use the tables as I will. No one
is on the dedicated server but myself.
Have a simple basic, no frills form
in Access 2K with ODBC linked (2.5
drivers) to the SQL server with
the admin setting to the root.
Using NT 4.0 SP5 with enough CPU
and RAM.
But two things keep happening that
I cannot explain for the life of me.
First, if I change information
(in this case the last name) in an
existing record Access warns me that
someone else is changing the data
and do I A) Drop Changes B) Overwrite
or C) Copy to Clipboard. So how
am I having this error if I am the
ONLY one in? Is the SQL part locking
the record, is it slow to update
because of a driver issue or is Access
2K not a MySQL player outside of
customer lookups???
Second, When I add a new record in
Access2K it would default a new
autonumber for the Client# and when I
move to a another record and come
back the data is entered. With this
no frills form attached to SQL It shows
no such next autonumber (even though
SQL KNOWS that already in the properties
and when I move off and move on the
fields all show a #delete error.
But when I close the form and open it
then it shows the information.
Now I personally could get used to this.
I could also use a requery statement
and live with that. But I have a
bunch of old women who are scared
to even look in a paper tray of
a printer when the print job won't
come out let alone get used to this
little difference. And I can tell
you now they will be scared they did
not enter it right and I will have
quadruple entries real quick.
How can I get the form to show the
infor and behave the EXACT same way
it did when using JET as the backend
and Access2K in the frontend??
If you are wondering why we even
bothered when we have all these
old scared women; don't ask me
ask the boss who must have SQL.
And NO I do not have god-like power
in this organisation I am just the
guy whom is expected to get anything
to work right.
Thanks for reading this huge post.
Last edited by reschool2003; 01-16-2003 at 10:04 AM.
-
Check number 4.9 on the linked page below. I had a similar problem before. I think adding a primary key solved it for me using access2k, even though the article says it only happens with 97. Show's how much they know! Let me know if this helps, and if not, i'll try to find something else.
-Furious
http://www.mysql.com/products/myodbc...Modified_error
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|