Replies

You can only use the auto tab on text boxes. So I guess I would create the combo box as unbound, and create a bound text box right next to it that is part of the tab order. Take the tab stop off of the combo box. Put an input mask and auto tab in the text box. It sounds like they’re probably going to know what they want to type in anyway, without using the drop-down from the combo. If they do use the combo, put an event in the after update to set the text box equal to the combo box. You could also add an event to the text box to check for valid data if you want it to limit to the list in the combo box.

That’s what I’d do anyway, but I’m usually finding my own strange ways to do things. I did try it on a small form with 3 fields. With everything autotabing it goes to a new record after the last field. If you want to force them to save you’ll have to put a hidden field in to make it loop on the same record. There are probably better ways that I don’t know about. Hope this helps.

In the properties for the controls on the form you can set the “auto tab” to “yes”. Select all the controls you want it for at once, then you only have to set it once.

In the properties for the controls on the form you can set the “auto tab” to “yes”. Select all the controls you want it for at once, then you only have to set it once.

Did you ever get a reply to this post? I have the need for an odbc driver or an informatix database to be used with Access. Thanks.

Did you ever get a reply to this post? I have the need for an odbc driver or an informatix database to be used with Access. Thanks.

It didn’t help shutting down or retyping on the criteria line, but I retyped the values in the parameters window also and that corrected the problem. Thanks for your help!

I am having similar problems. DB was developed with windows 2000, office 2000. Moved to Windows XP, Office XP. I get the same OLE server error. Only difference is my database doesn’t have any automation in it. So your problem may be related to something different.

I am also getting errors when trying to import objects from an access 2000 database to an access 2002 database, even tho it is running the db as 2000 (wasn’t converted). It kicks me out of access entirely.

I’d appreciate it if you would post again if you find anything, or send me email. This board is usually my only support line, since no one else here works with Access. I couldn’t find anything on Microsoft’s site.

I’ll try the reinstall. I had done everything else you mentioned.

Thanks. Frances

I know what you mean about the developers who don’t create these relationships. But I know for sure they were there at one point because I used them several months ago to determine how a number of tables were related so that we could import data. It’s sounding to me like I’m going to have to have them work on it.

I was just hoping there was a quicker way using that system table to get these back. Thanks for your input.

Frances

If they have to be added back in I’ll get the software vendor to do that. I would have no idea of the relationships because there are too many tables. It’s a backend database which is on a network and used by about 3 people simultaneously. I’m not sure what the front end is written in. It does have a lot of both reports and forms. Are you thinking that would somehow affect these?

Thanks for your response.

I just tried F5 and it does the same thing. Another quirky thing, when I hit F5 it redisplayed the same info as before, but I didn’t have ANY floppy in the drive. It didn’t give me any error. Not only that, I can actually double-click a file and it will open — without the correct disk being in there. ???

Earlier I tried to uninstall the drive and reinstall it and ended up getting a serious windows error that I had to do a repair on to just get my machine back. But the floppy problem was still there.

Since it doesn’t appear to be SP1 in general, any ideas of what else/ where else I can check? Thanks.

To be honest I don’t remember why they were ever defined as decimal. It was a long time ago. I have since changed that. But back to the initial question, I added a field to a test table defined as decimal and it too showed up as “delete query” in the documenter. It has to be a bug. The reason it initially worried me was the reason I was even looking at this table was because the user said there were rows mysteriously missing. Then when I saw that “delete query” listed, I wondered if it could have had anything to do with it.

Anyway, they’re no longer decimals so that shouldn’t come up again. Thanks for your reply.

Thanks for both of the suggestions.

I may have been going into “Advanced” one screen too late in the wizard.

Another thing that made a difference was the first rows returned in my query didn’t have anything in the date fields. When I changed the order of the query so that the first rows that show in the wizard have data in them, it seemed to work. It kept the formatting that I created with the calc statement in the query. For some reason those nulls showing up first was throwing it off.

Thanks for your help.

Thanks for the info. That works. Had to edit the registry and add the .dat extension. The article number is Q245407 if anyone else is interested.

Thanks again.

I was already running SR1, but I uninstalled office and reinstalled it to be sure. It was still happening but I found another article in the knowlegebase (Q240826)that said to take the check mark out of the Name AutoCorrect box under Options, in addition to SR1. So far this seems to be working. Thanks for pointing me in the right direction.

That’s exactly what I needed. Thanks so much!