Community
Showing results for 
Search instead for 
Do you mean 
Reply

Errors: "Object reference not set to an instance of an object", or "Table doesn't have a primary key"

New Member
Posts: 12
Country: United States

Errors: "Object reference not set to an instance of an object", or "Table doesn't have a primary key"

I am a longtime ACT! user since before 2000. I ahve created many ACT! databases and customized templates.

 

Ever since we upgraded to ACT! 2007 and subsequent versions, we have been experiencing the same two errors repeatedly following using the "Lookup" function.

 

"Object reference not set to an instance of an object", or "Table doesn't have a primary key"

 

These two errors, frequently occur after running a several lookups or after scrolling through the contact records results following a lookup.

 

Tried each of the following fixes and still have same two errors.

 

Ran Check Database

Ran Repair Database
Ran Reindex Database

Ran Detach Database

Ran Rebuild Schema

Ran Rebuild Security
Ran Rebuild OLE/DB Report Obejcts

Ran Rebuild OLE/DB v2.0 Report Obejcts

Rebuild Sync Objects

Created a copy of Database and ran on completely different server

Created blank copy of Database and ran it on a completely different server

 

We are running 2011 Premium now on Server is running Server 2003 SP2, SQL 2008, Quad core with 4 GB RAM

All Workstations are running XP Pro with 4 GB of RAM

Mike Shannon, theforeclosureguy
Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Errors: "Object reference not set to an instance of an object", or "Table doesn't have a primary key"

Mike,

Very good ideas putting the database on another server and creating an empty copy.  Since they had the same issue, It sounds like the issue is within the format/schema of the database.  As another test > open the ActDemo (or create a brand new database) and test with it to see if the errors occur.  

 

If the errors do not occur in the demo/new database, the next option would be to add your customized fields to a new database and then import your data from the original database to the new one.  Depending on how much customization you have done to your database, this may or may not be a daunting task.  Here is an article that explains the steps for importing a database: KB Article 17539

Greg Martin
Sage
New Member
Posts: 12
Country: United States

Errors: "Object reference not set to an instance of an object", or "Table doesn't have a primary key"

HI Greg,

 

First of all, can someone explain to me what each of these two messages mean?

 

Object reference not set to an instance of an object"

 

"Table doesn't have a primary key"

 

I actually created a new database using ACT! 2009 a few months back and paid a person to come in and re-type/re-enter each field from scratch and saw the error show up in the brand new Database.

 

Is it possible for the Field names themselves to create such a conflict?

 

Too many letters in field name?

Field name similar to table/schema name or referenece?

Inappropriate field name format?

Too many fields?

Table overflow issue?

 

 

 

Mike Shannon, theforeclosureguy
New Member
Posts: 12
Country: United States

Re: Errors: "Object reference not set to an instance of an object", or "Table doesn't have a primary key"

is there a limit to the number fields a database can contain? Is it possible the spelling of a field name, or length of a field name is causing the database to have an error locating the primary key after completing a lookup or running a sort which is when the errors most frequently occur.
Mike Shannon, theforeclosureguy
Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Errors: "Object reference not set to an instance of an object", or "Table doesn't have a primary key"

The way the database/SQL works there isn't a limit to the number of fields that can be added.  Fields are contained within tables - as tables fill up with new fields, they create additional tables.  So, while the number of fields would be unlimited - as additional tables are added it would affect performance. 

 

When creating the fields, the names would have to meet the limiting criteria or it would not allow you to complete the creation of the field - so it's hard to think that the name/length would be the cause, but hard to be sure if the database was created in earlier versions of ACT! which may have had different naming limitations. 

 

Have you tried setting the layout(s) to the 'Basic Layout' and reset your Contact List columns to default > then testing for the error?  (Setting the layout and columns to basic/default would keep your custom fields from displaying and possibly affecting the action)

 

Noting that you tried the database on a different server with the same results (meaning it is most likely database specific), have you opened the demo or created a new databse and tested for this error?  Doing this would verify that it is or isn't database specific.

 

How many custom fields have you created in your database?  You can create a list of your fields by using Actdiag > Database List > highlight database > Actions > Database Reports > Database Structure > Fields List to CSV File.

 

Greg Martin
Sage