Re: Newbie, True and False
- From: "Scott Morris" <bogus@xxxxxxxxx>
- Date: Mon, 2 Apr 2007 08:39:28 -0400
I have started conversion of the code that was originaly written for
Access. All commands, Insert, Update etc work fine with MySql, but not
with MsSql. The only real problem that I can see is the True and False
fields. I really don't want to have to write completely seperate routines
for each database back end.
Laudable - but highly improbable (IMO).
Also, pulling in a field and setting a CheckBox.Checked state to True or
False is easy if the return value is True or False.
I have thought about writing some kind of parser to check for certain
keywords and replace them, but I cannot guarantee that the users are not
going to use the words True, Flase or even 1 or 0.
Any help would be greatfully recevied as I currently have no idea how to
get around this!
Neither do I as I don't use Access. I suggest you post to an
Access-specific NG since that is the crux of the issue here. As I said
earlier, there is no boolean datatype in sql server. Since moving an Access
system to sql server appears to be a common activity, I expect that this
topic has been covered in an Access NG.
.
- Follow-Ups:
- Re: Newbie, True and False
- From: tclancey
- Re: Newbie, True and False
- Prev by Date: Re: connection issue from our developer
- Next by Date: Re: Newbie, True and False
- Previous by thread: Re: connection issue from our developer
- Next by thread: Re: Newbie, True and False
- Index(es):
Relevant Pages
|
Loading