Database will not update all fields from html form i created

[Kerusso]

I have an older .mdb database. I recently purchased Access 2010. I loaded my database and all works fine. I created about 6 new fields in this database. I have a form that I created a ways back that I use to update my database from my localhost site. I have a view record page and all fields show as desired. I have a form button to edit the record I am viewing. I updated my edit form that I have been using reflecting these new fields and I can change the data in the fields that I had previously and that data be reflected when i go back to view the record in my view record form. However, if i change any of the data in the new fields I have created that information is not being updated in my database as the other fields are. Is there something in Access 2010 that keeps me from updating these new fields? I am at a loss on how to get it to update. Any help would be greatly appreciated.

[ItsMe]

...I have a form that I created a ways back that I use to update my database from my localhost site...

What does this mean? Can you offer specifics how you created this form? Is this an Active Server Page?

[Kerusso]

Yes...it is an Active Server Page. The form I use to edit the record calls another Active Server Page that validates my entries. Once the validation is complete I use the objRS.Update. I have used this same form with no problems before. It was after I created the new fields that I seem to have problems. The fields that were already in the database prior to using Access 2010 I can change no problem. It is only the new fields that won't change or update. Once the validation is complete and the database updates I use a redirect to go back to my view database record page. Any changes made to those fields that were already there when i first created the database a few years ago update no problem. The other fields I created within the past week or so with Access 2010. It is those fields that will not update. My database was originally created with Access 2000.

[ItsMe]

AFAIK Access 2010 does not support ASP. DAP and ASP have been deprecated. The ODBC connection required for the ASP to work is going to need to use the correct drivers. The drivers will be good to work with MDB files.

I will guess your editing the MDB file using the later version has caused issues with the file, even the it is still an mdb format. I will guess the change is happening during JIT compilation. In other words, open the file changed its characteristics. However, I am not an expert in this and could be wrong. I create mdb files using Access 2010 and are then used with Access 2010 RT, no problems. I use a certain neurotic approach that I believe prevents unwanted results. Could be all in my head.

Anyway, maybe you are creating a fancy field in the table that the ODBC drivers do not like. Although, the MDB file format should not allow/reject such an edit.

[Kerusso]

Not sure exactly what you mean. All fields are being updated with the exception of the fields i added using Access 2010. The other fields update no problem. My .asp pages connect to the database no problem anywhere else. I can load Access 2010 and look physically at a record that I have updated from the .asp file and the fields are updated with the exception of the ones I noted. None of the fields are fancy fields. All are plain text fields. What driver should I be using? I assume this is the driver I am using: Microsoft.Jet.OLEDB.4.0. This is what I use to open the database:
DIM objConn
Set objConn = Server.CreateObject("ADODB.Connection")
objConn.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & Server.MapPath ("/database/BAM.mdb") & ";"
objConn.Open

Is there another driver I should now be using? If so where do I get it?

[ItsMe]

That is the driver. Not that I have every detail memorized but, you say it works so that is the one then. The point is the driver is specific to mdb files and ASP pages that were created with Access 2003. You are causing edits with Access 2010. Obviously this did not work. So I am focused on this point.

Now that I am thinking about it more, I am starting to remember some of the process of creating an asp using 2003 and now my head hurts.

I believe the code created in the .asp file is going to call the DSN by name. Your issue may be in the field names, as they are defined in the HTML of the asp. Perhaps you can take a look at the code there and see where things are not working (look for differences).

EDIT: I believe there are other supporting files created along with the asp. The creation of the asp file is an act of publishing and there are supporting files IIRC.

[Kerusso]

Thank you for your timely replies...should have said that earlier..my bad. I checked that issue first off. Have been known to misspell a number of times. I literally checked every jot and title. All the form names and field names are spelled correctly including caps where needed all in accordance with the way they are spelled in the database itself. Just cannot figure out why those fields that I added after I started using Access 2010 will not update and the others will. What is this me.Dirty thing I have been reading about? Is that something I need to put into my code and if so where?

[ItsMe]

Dirty is a member of the Form object. It might be a member of the Report object now too, dunno. Anyway, it is a property that if it is True then the form's recordset has not been saved and committed to the table.

As for your asp. You are going to need an older version of Access to publish changes. That's how I see it. Something is not getting edited that needs to be. Unfortunately, I do not have any samples to look at other than some old asp files that are not connected to anything. Looking at the HTML, nothing is jumping out at me.

I think there is some black box stuff that happens when you publish an old school asp. So any edits to the table require the asp to be published again.

[Kerusso]

Well thanks for your help. I have a form I created inside Access itself that works just fine. I just wanted to be able to do it on the fly inside my .asp programs as I was doing before but I guess we can't have everything we want. LOL...thanks again.