By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,473 Members | 3,505 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,473 IT Pros & Developers. It's quick & easy.

Converting from Access 2000 to Access 2003, execute for a sql insert, update not working

P: n/a
Hi all,

I'm sure someone knows about this problem. I have an Access database
designed in Access 2000, connected to an ORACLE 8i back end. On the
ORACLE side I have stored procedures, triggers and views that kick off
at different times. My Access 2000 database works well.

Problem:
I converted the database to Access 2003 am using ORACLE again as my
back end (they have updated the drivers in Oracle to 9i). I an trying
to execute a querydef, when I follow both programs in 2000 the .Execute
executes, when I run it in 2003 it hits the .execute and seems to goto
the On Error GoTo proc_err procedure which brings up a message that
there is someone putting the same information into the table. Can
anyone tell me why the .execute works in 2000 but not 2003 and is this
a problem with XP compared to 2000.
Set qdf = CurrentDb.CreateQueryDef("", strSQL)
With qdf
.Connect = strConnect
.ReturnsRecords = False

'Perform the insertion, allowing 3 retries on error in case of
contention
intRetry = 0
On Error GoTo proc_retry
.Execute
On Error GoTo proc_err

Feb 13 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Gox
Ch***************@pw.utc.com wrote:
Hi all,

I'm sure someone knows about this problem. I have an Access database
designed in Access 2000, connected to an ORACLE 8i back end. On the
ORACLE side I have stored procedures, triggers and views that kick off
at different times. My Access 2000 database works well.

Problem:
I converted the database to Access 2003 am using ORACLE again as my
back end (they have updated the drivers in Oracle to 9i). I an trying
to execute a querydef, when I follow both programs in 2000 the .Execute
executes, when I run it in 2003 it hits the .execute and seems to goto
the On Error GoTo proc_err procedure which brings up a message that
there is someone putting the same information into the table. Can
anyone tell me why the .execute works in 2000 but not 2003 and is this
a problem with XP compared to 2000.
Set qdf = CurrentDb.CreateQueryDef("", strSQL)
With qdf
.Connect = strConnect
.ReturnsRecords = False

'Perform the insertion, allowing 3 retries on error in case of
contention
intRetry = 0
On Error GoTo proc_retry
.Execute
On Error GoTo proc_err


Hi Christine,

I have a same problem like you, but in my case this not work:

db.QueryDefs.Delete NameOfQuery

On some client machine (Win XP + SP2, Office 2003) works well, but on
others machine (same config -> Win XP + SP2, Office 2003) not work.
I think problem is Access config or Jet

People help us!!

Feb 14 '06 #2

P: n/a
Hi,

I do know that we have the updated SP for Jet the latest one. Some of
my digging I found there is another SP for Office 2003, I know my
company needs to install Office 2003 SP2. Is there a work around for
converting an Access 2000 program to an Access 2003 program? Do I need
to import the forms, modules, reports & classes, like we had to from 97
to 2000? Do I need to rewrite this program in 2003 or can I convert &
then redo the forms & reports?

Thanks,
Chris

Feb 15 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.