December 1, 2015 at 2:30 am
I developed an Access (2010) frontend for a big company, linked to SQL Server (2012) and its performance is very good! Only one table is not updatable because of missing primary key. As soon as I add the primary key to this table (placed at a unique increment field, int, functioning as Autonumber) the whole Access frontend gets incredible slow!! Access seems busy all the time with some activity, clicking on the close button of the main form for example takes minutes before it responds.
Tried so many options, but do not have any clue anymore and the presence of the key is an absolute must in order to make changes and editing.
Does anyone know a solution/cause for this?
Many thanks in advance for support!!
Regards,
Rob...
December 1, 2015 at 2:35 am
Rob
What query is executed when the Close button is clicked? Please will you post a CREATE TABLE statement for the table in question?
John
December 1, 2015 at 2:39 am
Thanks for your reaction John!
There is no query at all behind the close button. It is just one of the many events that goes extreme slow as soon as I add the PK in SQL Management Studio. The Access frontend consists of VBA code managing all desired functions. I dont use queries in SQL, SQL only serves for table-environment, the frontend directs and controls, all built-in.
As soon as the PK is removed, everything works great in the frontend!!
December 1, 2015 at 2:41 am
PS. I am an Access & VBA developer, I use SQL only for the placement of the tables...
December 1, 2015 at 2:57 am
December 1, 2015 at 3:01 am
But why adding just one key causes so much horror (horror it is right now!)? Other same kind of tables are functioning so well....
December 1, 2015 at 3:04 am
I'm afraid I can't answer than until I know what your table looks like and what queries are running against it.
John
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply