Prev: Detail Background
Next: How to synchronize between form inside MS Access to outlook ca
From: Anthony Ching on 21 Feb 2010 21:37
I am using Access 2007. When I use Developer's Extension to create .accdr
with Access Runtime to run on machines with Office 2003 only, the above
message comes up when I tried to use the "Update" statement. the .accdr works
fine on my machine though.

The statement I tried to execute is:

Dim strSql As String
Dim cn As ADODB.Connection

On Error GoTo Change_Err

Set cn = CurrentProject.Connection
strSql = "UPDATE [User Identification] SET [Password] = '" & ([New
Password]) & "', [Date Last Change] = #" & Now() & "# WHERE [User ID]= '" &
TempVars!CurrentUser & "';"
cn.Execute strSql

Password and User ID are both alphanumeric.

Can someone help. Thanks.

--
Anthony
From: Debra on 21 Feb 2010 23:50

"Anthony Ching" <AnthonyChing(a)discussions.microsoft.com> wrote in message
news:5549B719-711A-46CC-8DD1-208B3CA79143(a)microsoft.com...
>I am using Access 2007. When I use Developer's Extension to create .accdr
> with Access Runtime to run on machines with Office 2003 only, the above
> message comes up when I tried to use the "Update" statement. the .accdr
> works
> fine on my machine though.
>
> The statement I tried to execute is:
>
> Dim strSql As String
> Dim cn As ADODB.Connection
>
> On Error GoTo Change_Err
>
> Set cn = CurrentProject.Connection
> strSql = "UPDATE [User Identification] SET [Password] = '" & ([New
> Password]) & "', [Date Last Change] = #" & Now() & "# WHERE [User ID]= '"
> &
> TempVars!CurrentUser & "';"
> cn.Execute strSql
>
> Password and User ID are both alphanumeric.
>
> Can someone help. Thanks.
>
> --
> Anthony

From: Jerry Whittle on 22 Feb 2010 09:52
I don't see anything obvious. My suggestion is to create a plain old query as
similar as possible to your code. See if there are any problems running it
that way.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"Anthony Ching" wrote:

> I am using Access 2007. When I use Developer's Extension to create .accdr
> with Access Runtime to run on machines with Office 2003 only, the above
> message comes up when I tried to use the "Update" statement. the .accdr works
> fine on my machine though.
>
> The statement I tried to execute is:
>
> Dim strSql As String
> Dim cn As ADODB.Connection
>
> On Error GoTo Change_Err
>
> Set cn = CurrentProject.Connection
> strSql = "UPDATE [User Identification] SET [Password] = '" & ([New
> Password]) & "', [Date Last Change] = #" & Now() & "# WHERE [User ID]= '" &
> TempVars!CurrentUser & "';"
> cn.Execute strSql
>
> Password and User ID are both alphanumeric.
>
> Can someone help. Thanks.
>
> --
> Anthony
From: Anthony Ching on 22 Feb 2010 20:26
Thanks Jerry. I tried that and the same problem appears. Can it be something
different between the 2003 and 2007 office jet engine. Btw, the database is
split and the data portion resides in a server.
--
Anthony


"Jerry Whittle" wrote:

> I don't see anything obvious. My suggestion is to create a plain old query as
> similar as possible to your code. See if there are any problems running it
> that way.
> --
> Jerry Whittle, Microsoft Access MVP
> Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
>
>
> "Anthony Ching" wrote:
>
> > I am using Access 2007. When I use Developer's Extension to create .accdr
> > with Access Runtime to run on machines with Office 2003 only, the above
> > message comes up when I tried to use the "Update" statement. the .accdr works
> > fine on my machine though.
> >
> > The statement I tried to execute is:
> >
> > Dim strSql As String
> > Dim cn As ADODB.Connection
> >
> > On Error GoTo Change_Err
> >
> > Set cn = CurrentProject.Connection
> > strSql = "UPDATE [User Identification] SET [Password] = '" & ([New
> > Password]) & "', [Date Last Change] = #" & Now() & "# WHERE [User ID]= '" &
> > TempVars!CurrentUser & "';"
> > cn.Execute strSql
> >
> > Password and User ID are both alphanumeric.
> >
> > Can someone help. Thanks.
> >
> > --
> > Anthony
From: Gina Whipp on 23 Feb 2010 00:50
Anthony,

Check your References... sounds like it might be Access getting confused
between the versions.

--
Gina Whipp
2010 Microsoft MVP (Access)

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"Anthony Ching" <AnthonyChing(a)discussions.microsoft.com> wrote in message
news:BDD69603-CB51-4F10-B265-250E42D7BBE3(a)microsoft.com...
Thanks Jerry. I tried that and the same problem appears. Can it be something
different between the 2003 and 2007 office jet engine. Btw, the database is
split and the data portion resides in a server.
--
Anthony


"Jerry Whittle" wrote:

> I don't see anything obvious. My suggestion is to create a plain old query
> as
> similar as possible to your code. See if there are any problems running it
> that way.
> --
> Jerry Whittle, Microsoft Access MVP
> Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
>
>
> "Anthony Ching" wrote:
>
> > I am using Access 2007. When I use Developer's Extension to create
> > .accdr
> > with Access Runtime to run on machines with Office 2003 only, the above
> > message comes up when I tried to use the "Update" statement. the .accdr
> > works
> > fine on my machine though.
> >
> > The statement I tried to execute is:
> >
> > Dim strSql As String
> > Dim cn As ADODB.Connection
> >
> > On Error GoTo Change_Err
> >
> > Set cn = CurrentProject.Connection
> > strSql = "UPDATE [User Identification] SET [Password] = '" & ([New
> > Password]) & "', [Date Last Change] = #" & Now() & "# WHERE [User ID]=
> > '" &
> > TempVars!CurrentUser & "';"
> > cn.Execute strSql
> >
> > Password and User ID are both alphanumeric.
> >
> > Can someone help. Thanks.
> >
> > --
> > Anthony


 |  Next  |  Last
Pages: 1 2 3
Prev: Detail Background
Next: How to synchronize between form inside MS Access to outlook ca