Entries by Victor Raj

This message started popping suddenly after my Access front-end for a SQL Server 2005 backend database got too big. Apparently this is activated when the number of objects (tables/forms/reports etc) exceeds some mystery threshold. You won't be able to do ANYTHING. As always, there are many solutions depending on what actually caused this generic message.

The one that worked for me - nicely I might add - was DECOMPILE.

<path to file> /decompile

This has to be done from the command prompt (Press Start and enter cmd and press enter). If the file or folders in the path contain spaces, enclose the <path to file> in quotes.

Microsoft's "Developer Evangelist" - Jennifer Marsman - came in at the combined invitation of the West Kentucky Dot Net Users' group and the Murray State Women in Computing/Technology on Thursday, October 21. She stayed on for one more day and visited several classes to share her enthusiasm and love for technology and Microsoft.

Roundabout-U interviewed her while she was on campus. See Jennifer's post on her blog for details

Ran into this error when my back-end database crashed on my application. I would be able to view the first record, but as soon as I went to the next record using either the navigation bar or the combo-box I use to find records I would get this error: "No current record"

Looked at the results of numerous google searches and found Allen Browne's solution quite handy. However none of his tips included my situation: failure while viewing data.

Turns out I simply had to relink my tables!

Sometimes simple solutions always evade us. I spent quite a few hours before I got to this. Hope it works for you!