I have found my problem...the problem was with access
asking for unique identifiers in each table. I might have had the
same identifier for two tables. Now it seems to be working.
Thanks for all who helped
STeve
- Original Message -
From: "Steve Siesel" <[EMAIL PROTECTED]>
To: <[EMAIL
to view the tables?
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 3/4/04, 2:47:51 PM, Steve Siesel <[EMAIL PROTECTED]> wrote regarding Re:
MS Access and MySql:
> Th
The Database was originally made in Access
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Steve Siesel" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, March 04, 2004 3:35 PM
Subject: Re: MS Access and MySql
What is `special` about thi
e -
> From: <[EMAIL PROTECTED]>
> To: "Steve Siesel" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Thursday, March 04, 2004 3:03 PM
> Subject: Re: MS Access and MySql
> Are you using ODBC Links or are you importing the table into MS Access
04, 2004 3:03 PM
Subject: Re: MS Access and MySql
Are you using ODBC Links or are you importing the table into MS Access
from MySQL? Are there unique constraints on the table to prevent
duplicate data from being entered?
>>>>>>>>>>>>>>>>>>
Are you using ODBC Links or are you importing the table into MS Access
from MySQL? Are there unique constraints on the table to prevent
duplicate data from being entered?
>> Original Message <<
On 3/4/04, 1:57:15 PM, Steve Siesel <[EMAIL PROTECTED]> wrote regardi
Mary,
Wednesday, August 28, 2002, 7:49:22 PM, you wrote:
MS> see my message re--- index problem
MS> ok when I do explain in this , it is not using an index for the
MS> AdminCoverage_writingagents table...
MS> SELECT admincoverage_writingagents.WritingAgentID,
MS> admincoverage_writingagents.Wr
simply
be
> high praise for MyODBC, but my Access app has no difficulty at all
talking
> to the database.
>
> Arthur
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: "Arthur Fuller" <[EMAIL PROTECTED]>
> Sent: Wednesday, August 28, 2002 1:57
o the database.
Arthur
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Arthur Fuller" <[EMAIL PROTECTED]>
Sent: Wednesday, August 28, 2002 1:57 PM
Subject: [Fwd: RE: MS Access and mySQL]
> wodya think?
>
>
> Original Message
>
re also abandoning Access.
If you have any specific questions, feel free to ask.
Arthur
> Original Message
> From: "Nicholas Stuart" <[EMAIL PROTECTED]>
> Subject: Re: MS Access and mySQL
> To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
&g
August 28, 2002 7:32 PM
Subject: RE: MS Access and mySQL
> Or you could just use the libmySQL.dll and handle everything yourself
> through VB.
>
>
> >>You will however need to download the MyODBC driv
True you could, but then that way you will loose portability if Jon (for
whatever reason) decides to move to another type of DB. Never used
libmySQL so I dont know how the speed is, but assume its as fast if not
faster then ODBC.
ODBC has the plus of being user friendly and of being an M$ Universa
gentid (WritingAgentId),
KEY writingagentslot (WritingAgentSlot)
);
-Original Message-
From: Mark Matthews [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 28, 2002 11:11 AM
To: Mary Stickney
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: MS Access and myS
Or you could just use the libmySQL.dll and handle everything yourself
through VB.
>>You will however need to download the MyODBC driver if you wish to access
>>MySQL through VB.
>>
>>-Nick
-
Before posting, please check:
h
Mary Stickney wrote:
> the join syntax is what is differnt between Access and MYSQL.
>
> in MS-SQL = indexs will be used on tables mentioned in the JOIN clause
> and they will not in MYSQL
This is not true. MySQL uses indexes in joins, if you've put them in the
right columns, just as in MS-SQL
I would strongly urg you not to use Access as the front end. The biggest
problem is that the Jet Engine/Access backend is pretty much completly
different then MySQL and you will run into problems with table structure
and the like. Also, using access as the front end has been extremly slow
when eve
S-SQL = indexs will be used on tables mentioned in the JOIN clause
and they will not in MYSQL
-Original Message-
From: Nicholas Stuart [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 28, 2002 9:40 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: MS Access and mySQL
I have been there
PROTECTED]; [EMAIL PROTECTED]
Subject: Re: MS Access and mySQL
I have been there done that with old access data, but no forms. Your
plans should be focused around what you know and what your systems are
tied to. Since its an NT box you could go with pretty much any language
ie java/vb/c++. VB would be
I have been there done that with old access data, but no forms. Your
plans should be focused around what you know and what your systems are
tied to. Since its an NT box you could go with pretty much any language
ie java/vb/c++. VB would be the obvious choice for ease of transfering
the Access VBA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan,
If you are going to be completely converting the Access db to MySQL,
and just using Access as the frontend, you will need to download
MyODBC:
http://www.mysql.com/downloads/api-myodbc.html
You can download either the stable or developme
Yes it is perfectly possible. I did that some months ago and it worked perfectly. I,
however, had to install MyODBC on the windows box. There is a good tutorial I used at
http://www.devshed.com/Server_Side/MySQL/ODBC/page1.html
Its a good tutorial By W.J. Gilmore.
Please take note of the deci
21 matches
Mail list logo
