Cannot create an instance of OLE DB provider “VFPOLEDB” for linked server “Opera”.

Unsolved

Msg 7302, Level 16, State 1, Line 1
Cannot create an instance of OLE DB provider “VFPOLEDB” for linked server “”.

Click here for one part of solution Social.msdn

in Server Objects > Linked Servers > Providers > VFPOLEDB > General tab > Provider options > Allow inprocess. Also, you can
change the InProcess setting with the following code:

USE [master]
GO
EXEC master.dbo.sp_MSset_oledb_prop N’VFPOLEDB’, N’AllowInProcess’, 1
GO

Then get a new message
OLE DB provider “VFPOLEDB” for linked server “Opera” returned message “Invalid path or file name.”.

Cannot initialize the data source object of OLE DB provider “VFPOLEDB” for linked server

 

Advertisements

Edit and Continue: Changes are not allowed when the debugger has…

 
Edit and Continue
Changes are not allowed when the debugger has been attached to an already running process or the code being debugged was optimized at build or run time
 
Probably more than one issue:
  1. Check that running in Debug mode

 

VB6 Add-Ins E.g. Class Builder

 
Normally located here:
      C:\Program Files\Microsoft Visual Studio\VB98\Wizards\
Then
      CLSSBLD.DLL
 
Run regsvr32.exe on these
 
API Viewer is in there somewhere
 

TRUNCATE TABLE – Generates error “Cannot find object * because it does not exist or you do not have permission”

 
Generates error
cannot find the object "%.*ls" because it does not exist or you do not have permissions.
 
TRUNCATE needs higher permission than DELETE FROM
Needs Alter control on table. This may be too high for entire schema and may really be too high for object.
So workarounds are:-
 
Use WITH EXECUTE AS SELF
AS SELF means execute as the person who created the s.p
 
 
http://msdn.microsoft.com/en-us/library/ms177570.aspx   – See permissions in this article
 
 
ALSO as a secondary note on TRUNCATE TABLE.
Truncate is not allowed if there are any Foreign Keys on the table
 
Steve
 
 
 

MS Access Fomatting when linked to SQL Server 2008 Dates

 
If linking to the new SQL Server date types, which are better in SQL Server and for the future, then MS Access 2003 treats them like strings.
To resolve:
 
  • Create a view in SQL Server 2008 and use CONVERT(datetime, MyDate) with optional ,105 on end.
  • Link to the view in MSAccess. Possibly renaming the view as the original linked table name, so that it will still work throughout existing Access design
  • You may need to set unique keys during linking process. This helps MS Access to know what are unique keys so that it will be able to update records if required.
  • Voila. Fixed

Steve

The procedure entry point IsThreadDesktopComposited could not be located in the dynamic link

Windows Live Writer. Error on entry

The procedure entry point IsThreadDesktopComposited could not be located in the dynamic link
 
I renamed dwmapi.dll to dwmapi.dll.bak and the error disappeared in UR, but God only knows what else that will affect. While running IE7 inside of UR there does not seem to be any problems.
 
SRS 13-Aug-2009
Did this and problem has gone away
 

MS Access 2007 Create MDE for use with MS Access 2003 or earlier

If starting with MS Access 2007 then making an MDE it is not possible to open this MDE from earlier versions.
You may think that saving the database in MS Access 2002-2003, then making the MDE would work. However it will not.

A solution:

  • Save as MS Access 2002-2003. Perhaps with a different name say MyApp2002.mdb
  • Open the new 2002-2003 database in MS Access 2002 or 2003 on another machine.
  • Make the MDE file from this machine as MyApp.mde
  • Voila !! Should now work

Another more complicated solution:

  • Distribute the application from MS Access 2007
  • Use MS Access 2007 run-time

Steve 13-Aug-2009

Object Oriented – OO – Visual Basic 6 Specifics – VB6

 
 
The word "Set" is often required. Omitting this in the following would compile but go through the Get routine instead and error in runtime.
 
Private Sub Class_Initialize()
    Set Me.Employee = New Employee
End Sub
 
 
In loops there are two options
Either Dim object as New instance inside loop. Then set to Nothing before next loop.
Do Until rsTD.EOF
Dim cTimeSheet As New clsTimeSheet
cTimeSheet.Employee.EmpeeNo = rsTD!EmpeeNo
Call cJS.colTimeSheets.AddTimeSheet(cTimeSheet, lngMaxEmp)

Set cTimeSheet = Nothing

rsTD.MoveNext
Loop

Or following with or without first New
Dim cTimeSheet As New clsTimeSheet

Do Until rsTD.EOF
Set cTimeSheet = New clsTimeSheet
cTimeSheet.Employee.EmpeeNo = rsTD!EmpeeNo
Call cJS.colTimeSheets.AddTimeSheet(cTimeSheet, lngMaxEmp)

rsTD.MoveNext
Loop

 
 
 
 
 
 
 

You may receive write conflict errors when you update records of a linked SQL Server table in Access 2000

 
 
Add a timestamp. Even if a view include this column.
 

Transfer SQL Server 2008 Database and Data to SQL Server 2005

 
11/08/2009 This works !! 
 
 
Also
 
 
SSMS > Select database > Right Click > Tasks > Generate Scripts > Proceed to "Choose Script Options" 
> Under "General" change option for Script for Server Version to SQL Server 2005 or 2000
> Can not see this but "If you are putting the database on a new instance for the first time, make sure the "Script Database Create" option is set to "True.""
> under "Table/View Options" select Script Data to True
> Proceed through rest of options choosing your preferences.