SQL Server introduced the BIGINT datatype in 2005 to keep up with Oracle. This is a cool thing especially for data warehousing. Unfortunately, ACCESS has the Integer and Long Integer datatypes. The Long Integer is equivalent to SQLs INT but no equivalent to SQLs BIGINT. This causes issues with ACCESS. If you link to a SQL table where the primary key is a BIGINT, the linked table will display #DELETED! in each cell. NO ITS NOT A SECURITY ISSUE!!! So if you have customers that need to view SQL data thru Access linked tables, there are work arounds BUT the BIGINTs will need to be changed to INT. Create an interface NOT in Access for your customers to view data if need be MOSS 07 is a quick solution if you're using it, else try VS.NET or JAVA web apps. yes its time consuming but you can't give all users Admin rights and SQL Server to play with!!!
Here's a link to your work arounds:
Subscribe to:
Post Comments (Atom)
2 comments:
OK HAVE A FAIR SOLUTION!!!
CREATE VIEWS OF THOSE TABLES IN SQL AND CAST THE BIGINTs TO INTs. GIVE RIGHTS TO CHANGE DATA IN THE VIEWS AND IT COMMITS THE CHANGES TO THE TABLES. PROBLEM SOLVED!!!
I have heard about another dbf file repairing tool. Besides, you can visit my blogs at: http://daspeac.livejournal.com/ or http://daspeac.blogspot.com/ where I’m trying to share my experience with regard to data corruption issues
Post a Comment