×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

problem with changing the example eshop quick start

problem with changing the example eshop quick start

problem with changing the example eshop quick start

(OP)
I have made some changes to the ershop that comes with Drumbeat 2000 Ecommerce I have only changed the product database

In the checkout page I get the following error after the submit order button is clicked.

Microsoft Cursor Engine (0x80040E21)
Multiple-step operation generated errors. Check each status value.
/oziwebhostingshop/media/javascript/IIS_Gen_3.0_Recordset.js, line 1141

I have searched the Microsoft KB but really found no answer to the problem - I have an idea that it may have to do with the setting of the date/time in the order file

any one give me some pointers
John

RE: problem with changing the example eshop quick start

There is probably a field in your orders database that depends on a field in your customer database, or vice versa.  Check both databases for fields that would be the same (i.e. customer_id, etc.) to make sure they exist.

RE: problem with changing the example eshop quick start

(OP)
thanks for the reply - I actually have found the problem maybe a small bug in drumbeat -
I deleted a recordset from the page however there was a contract that set a session to one of the fields of the recordset. When I deleted the recordset it deleted all contracts relating to that recordset but not the session contract thus when I published the line of code set the session to null which then created the problem in another page.

drumbeat was probably right - it deleted all contracts with the recordset as primary reference - the session contract had the recordset as a secondary reference thus I should have deleted the session contract manually

silly me.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close