Update or CancelUpdate without AddNew or Edit

[speakers_86]

I have an odd error occuring. I have two forms. One is frmOverview and has four subforms that give a synopsis of different missions. These subforms have hyperlinks that go to the frmMissions were data is added or edited. If I use the hyperlink to go to MissionID=1 and try to edit any field, I get the update error. There is no code behind the fields I am trying to edit. I do not get the error when frmOverview is not used. Now the odd thing is that this behavior only seems to happen where MissionID=1. I cannot duplicate it with other records. What's going on?

 

[speakers_86]

I fixed this already by setting dirty to false. I'm not sure how this is required though.

 

[HiTechCoach]

This is a common issue when you are modify the same record from multiple places.

By using the Dirty=False to save the record, then the next operation has exclusive access to the record. and is happy.

<off topic>
Your siggy is interesting. Since Office 2010 SP1 I moved all my client from 2007. The Access 2010 ribbon is much improved. I dread it whenever I have to use 2007.
</off topic>

 

[speakers_86]

I absolutely hate the 2010 ribbon. The whole backstage concept is bad. I like it in 2007. I modify the ribbon without any issues, and all of my navigation in this project is done in the ribbon. I've removed as much of the defaults as I can. The only default navigation I have not been able to get rid of is the page selectors in reports. This project is actually in use where I work, and is working well. I'm just working on an update.

My big issue with 2010 stemmed from my dev pc being 2010 and some old work stations being 2007. The accdb format is NOT backwards compatible.

 

[HiTechCoach]

My big issue with 2010 stemmed from my dev pc being 2010 and some old work stations being 2007. The accdb format is NOT backwards compatible.

Well that is not a 2010 issue but an environment (IT policy) issue with mixed version of Access.


I have seveal commercial apps that are an accde front end. It is current run bt 2077, 201, and 2013 users, most with the runtime version.

I created the database with Access 2007. I do almost 90% of the modifications in 2010. To begin testing I have a VM with Windows 7 32bit and Office 2007. I use this to create the .accde for deployment. I then test it will 2007, 2010, and 2013.

I have yet to have any backward compatibility issue with a .accdb created with 2007 and modified with 2010 ro 2013.

There are lots of create GUI satuff that only works with 2010 and later. The 2007 crete accde looks great in 2010 and 2013. The cool UI stuff is just ignored in 20/07.

I don't know how I could work effectively without having a Virtual Machines with the different versions Office.

 

[speakers_86]

True, but at the time when I had 2010, all of the machines I was deploying to were 2007. I put in tons of work and tried to test it on the end user's terminals and got an unrecognized database format error. I had to go to an old backup, move it to an mdb, and redo much of my work over. To me, the risk is not worth the reward. And the reward is a 'better' application. I think 2007 was just fine, and Microsoft found ways to change it to sell a new version. Like I said, the backstage is terrible. 2013 is even worse. Sure, 2007 could probably use some improvements, but nothing drastic.