On Mon, Apr 4, 2011 at 6:04 PM, Theodore Ruegsegger wrote:
> It would never have occurred to me to set up a MySQL (or PostgreSQL)
> backend yet still retain Access as the front-end, but no doubt you
> have your reasons.
>
I've done some Access work, years ago using only the MS Jet database engine
Stephen wrote:
> At work, one of the people
> here setup an MS access database application which is quickly turning
> into a nightmare because it does not use a real database as a back end.
> So I'm thinking that perhaps I can help them by setting up some tables
> in my mysql database server I hav
I've configured this before and yes, the process was fairly straight
forward. There was just one main gotcha that I found, which was something
to do with the autonumber value access uses to create primary keys. Forgive
me, it's been probably 5 years and the exact nuances escape me at present.
I
I've googled this in the past, and I found several HOWTOs that
appeared to indicate that it's fairly straightforward. I never got around
to trying it, though.
On Mon, Apr 4, 2011 at 3:20 PM, Stephen Adler wrote:
> Hi people,
>
> I believe the answer to my question is yes, but hearing it from on
On Mon, Apr 4, 2011 at 3:20 PM, Stephen Adler wrote:
> Hi people,
>
> I believe the answer to my question is yes, but hearing it from one of
> you guys will give me the warm fuzzies... At work, one of the people
> here setup an MS access database application which is quickly turning
> into a night
Hi people,
I believe the answer to my question is yes, but hearing it from one of
you guys will give me the warm fuzzies... At work, one of the people
here setup an MS access database application which is quickly turning
into a nightmare because it does not use a real database as a back end.
So I'
