July 2, 2007 at 10:45 am
My client uses an Access front end currently. He would like to link these tables to SQL Server because of the maintainability and recovery. I have used the upsizing wizard to do this and it linked the tables to a created database in SQL Server. However, there is a problem now with the Access front end. The front end used forms that had drop down bars. Now these bars come prefilled and when you try and change them, the machine just beeps at you. I was wondering if anybody had ever seen this problem and what they did to fix it.
-Kyle
July 5, 2007 at 8:48 am
When refering to "drop down bars" are you talking about Combo Boxes? If so do you have same problem with Text Boxes?
July 9, 2007 at 10:44 am
Sorry, I am having problems with the comboboxes, and with the text boxes. I am thinking there may be a connection problem with the server.
July 12, 2007 at 9:03 am
In the original Access table design, were those problem combo-box fields created as "lookup" fields? That is to say, if you open the Access table in datasheet view, do you see drop-down lists for those fields? That might be the source of the problem. The upsizing wizard might be using the display field datatype instead of the underlying field datatype, or vice-versa.
Another quick way to check would be to compare the datatype for one of those fields in Access to the converted SQL Server datatype. If they don't match, that's a problem.
If that is the case, you might have to remove the lookups from the Access fields in the table, then modify your forms to re-establish the lookup features.
One more thing to keep in mind is that an Access autonumber field contains a value as soon as you begin creating a new record, but in SQL Server an identity column doesn't have a value until after the record is saved.
Hope that helps.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply