Access is Hiring!

Why JET have so many problems with autonumbers? There are a lot of bugs (duplicate counters, issues with SQL Server, etc) that affect autonumbers keys in certain conditions... Zac, this is a feature of Access that MUST work fine: it's very important! Rose

Other question: In my opinion SubDatasheets are very useful, but they work only in DataSheet wiew... Why Continuous Forms doesn't support SubForms (including A '2007)? Rose

Hi Rose, You shouldn't be having problems with duplicate autonumbers, if you have updated the JET database engine to SP-8 on *ALL* PC's that touch your database. You very well may need to fix any tables that were created with a service pack of 3 (I believe) or lower of JET. I believe the dup. autonumber issue was fixed with the release of JET SP-4. How to keep a Jet 4.0 database in top working condition support.microsoft.com Within this article, follow the links that read: Verify that the latest operating system service pack is installed Verify that the latest Microsoft Jet service pack is installed Verify that the latest service pack for your version of Office is installed

I also recommend making sure that the latest MDAC (Microsoft Data Access Components) files installed on all PCs: www.microsoft.com/.../details.aspx Doing these things will help ensure that your time spent working with Access is productive, so that you are not battling some problem that has already been fixed with a service pack. Good Luck on your application!

Tom is right-on Rose. If all the suggestions he has made don't help you, please feel free to send me email with a detailed description of exactly what behavior your seeing as a step-by-step list that so we can reproduce it here in Redmond, and I'll investigate whether this is a known issue.

I had same problems with autonumbers like Rose said. Also I've lost my DB in compression process on close A2007!!! My customers explain to such problems. In my case was not problems with power-down and viruses. I saw message like "database with name MyDB.mdb already exists" And after convresion my A2003 app to A2007 in date fileds and some big values customers gets ### symblos like in Excel. I guess, users could not modified reports or forms in compiled application. At least in runtime mode all must be shown correctly.

Sorry for mistake. You should read "complain", not "explain"

The ### is actually a feature of 2007 indicating to your users that numbers are getting clipped. We were concerned about people making bad decisions because of truncating numbers. You can turn off the behavior in the Access Options | Current Database | Check for truncating numbers option. We are always interested in repro cases where databases would be lost during compact and repair. If you can reproduce it--we would love to look at the issue. As for the autonumbers problem--if you can reproduce the error I would recommend contacting our support team with repro steps so that we can take a look at the issue. There is a well defined process for getting patches to issues like this but we have to work through the system to make it happen.

Thanks for tip - You just save a few hours for me! :-) When file just disapperars last time was only this Monday - after compacting DB I get error message and not find the file!!! God thanks I've got fresh backup file and just restore it and modifid all that I can remember. And for last 2 montes that is second case personally for me. Another one case was few week ago with my customers, but they use removable HDD to store DB and two week ago this computer go to service..... But scheme of fault is the same. Message in compacting process and they have corrupted file - I've got no files at all all my 2 cases.

Maxim, was this file in an Offline folder on Windows Vista by chance? There are known issues with that configuration, and we advise against keeping Access databases in Offline folders until you've installed both the upcomming Vista and Office SP1 releases.

All operation was with XP home/pro, A2007

Would you send me mail directly including detailed reproduction steps which cause the file to be deleted and we'll investigate to see if this is something that has been addressed in the upcomming SP1 release? (zacwood@microsoft.com)

Is it possible to create a DSN-less connection to MySQL server? See www.utteraccess.com/.../showflat.php I'd like if Microsoft Access Team could open a forum to help programmers solve their problems. There are many forums on the web, I know, but there are many questions without replies or with unclear solutions.

To Zac: Unfortunally I can't... If it appear next time, maybe I get mad, but I'll wright down all what's happend and send it to You. :-) I use Access more than 10 years and 3 cases due last 2 month... It's too much... I just few weeks ago delete crashed DB's, include the one with problems autonumeration... Interesting fact about this fault - I'm re-create autonumbers field, but they was not work properly again (after about 3000 records) and then I create new mdb file and migrate this DB. DB contains near 40 tables and problems gets only with one most usable table. To Vladimir: It was only Access file. One case - tables in mdb, another one - linked table to local(!!!) machine.

To Zac: Unfortunally I can't... If it appear next time, maybe I get mad, but I'll wright down all what's happend and send it to You. :-) I use Access more than 10 years and 3 cases due last 2 month... It's too much... I just few weeks ago delete crashed DB's, include the one with problems autonumeration... Interesting fact about this fault - I'm re-create autonumbers field, but they was not work properly again (after about 3000 records) and then I create new mdb file and migrate this DB. DB contains near 40 tables and problems gets only with one most usable table. To Vladimir: It was only Access file. One case - tables in mdb, another one - linked table to local(!!!) machine.

Zac!!! I've got DB with autonumbers problem. How should I send it to You?