Even assuming Access has an object named dbo.SupperSummary, then the Jet SQL syntax is different from T-SQL and requires an asterisk (*) after the DELETE command. T-SQL syntax, in use on the server, allows such a command. The first sentence makes sense and would be expected to work. Still getting same error when I use "Delete from dbo.SupperSummary" in VBA. It ran on the Server as "Delete from SupperSummary".
Why would your code use that reference unless you'd seen it that way in Access (You certainly wouldn't have seen it like that in SQL Server). I'm very curious as to how this came to be if it's shown in Access as dbo.SupperSummary. From my limited memory, this is what I would have expected to see for the linked table within Access. I did notice though, that post #1 refers to it as dbo_SupperSummary. Unfortunately I no longer have access to a SQL Server to play with :-( Please refer to the following instructions to remove Spy Sweeper from your. Tool ny c th g tn gc cc phin bn Office t 2007, 2010, 2013 ,2016 v Office 365 bn ch cn n 1,2 click l c. Local IT really does not want to re image if at all possible. When this happens, we have to use our cleanup utility to remove the program. I had local IT try to uninstall via safemode, but he said the error came up with the error 'the language for the uninstall is not available' I have tried the Microsoft fix it 50450 that is supposed to force uninstall office and remove any leftover files, but no dice. However, the Spy Sweeper uninstall will sometimes become corrupted and fail to work.
Access runtime is free and allows Access databases to be run on any PC at zero. In 2010 you can also sign an accdb or accde front end (so I am told). In 2007 you can sign an mdb or mde Front End or an accdb of accde package. If you are looking for something else let me know. Usually Spy Sweeper will uninstall without problems from the Add/Remove Programs menu in the Control Panel. The VBA component in all MS Office applications includes the facility to digitally sign. Once the last system has been installed switch to using Access 2010 and continue to distribute MDEs. Keep on using Access 2002 to create the MDEs. If you have your own menus youll have to make the setting change to remove the ribbon so your menu is not put in the ribbon Add-Ins section.
But now I realize it isn't that apparent it is the error description. Install the free Access 2010 runtime on those PCs. If a client doesnt have Access 2000 (or later), I currently distribute Access 2000 Runtime along with the application.
SQLStg = "Insert into dbo_SupperSummary (Crew, Asset, Quality, Operator_ID, StartTimeStamp1 VALUES (SummaryData.Crew, SummaryData.Asset, SummaryData.Quality, SummaryData.Operator_ID, SummaryData.StartTimeStamp1)" SQLStg = "Delete * from dbo_SupperSummary" Set SummaryData = MyDb.OpenRecordset("SupperSummary", DB_OPEN_TABLE) Set SQLSummaryData = MyDb.OpenRecordset("dbo_SupperSummary", DB_OPEN_DYNASET) Set dataarea = MyDb.OpenRecordset("dbo_DATA_AREA", DB_OPEN_DYNASET) Set MyDb = DBEngine.Workspaces(0).Databases(0)