|
| Sql Server tables cannot be imported into my analysis |
| Iniciado por Meredith GUY, 01,mar. 2020 13:01 - No hay respuesta |
| |
| | | |
|
| |
Miembro registrado
7 mensajes |
|
| Publicado el 01,marzo 2020 - 13:01 |
Good day all
I am trying to develop a WINDEV application, using version 24, against a Sql Server database. The problem I am experiencing seems to be due to the fact that the database I am working against has its tables in 3 separate schemas – in other words, the tables do not exist in the usual dbo. Schema.
I have tried all the possible connections except for the PC Soft native Access SQL server. I have only recently purchased the software and wish to avoid additional expenditure on the native license, if I can avoid it.
The problem occurs as follows:
I create a new project. I then, via the Analysis menu, select the Import button, and the ‘import the descriptions of files/tables’ option. I then select the OLE DB option. I then select the Sql Server (Sql Server Native Client 11.0) option (and I have tried the Sql Server (Microsoft OLE DB Provider for Sql Server), ODBC Access via OLEDB and Microsoft OLE DB Provider for Sql Server, all with the same result).
I then create a connection to the local Sql Server database. I then select the ‘Access the data in its current format directly’ option. I am then presented with the screen showing me the files I can import on the left hand side, and I can move these to the ‘Files/Queries to import’ screen. At this point, even though the tables are in different schemas, I can see them all in the ‘Files/Queries of the database’.
Once I press the validate button to continue, I am told that Errors occurred while importing the structure of the database’. I receive the following error for each table (the RefCountry is the table in this example).
Unable to open ‘RefCountry’ table.
OLE DB Access Error.
Error number 170129.
Failure Opening file.
System Error Details:
Description = Invalid Object Name ‘RefCountry’".
Source = Microsoft Sql Server Native Client 11.0
Sql State 42502
Error Number = -2147217865 (0x80040e37)
Native Error Number = 208 (0xd0)
I contacted support and was given various solutions, none of which worked. I then searched the forum and found the following link, which seemed promising: https://forum.pcsoft.fr/en-US/pcsoft.us.windev/44881-windev-sql-not-using-dbo-schema/read.awp…. I tried this, and it worked for most of the tables. For the remainder, even though they are now all in the dbo. schema, I get the following error message which is different to the old message.
Unable to open 'RefCountry' table
OLE DB access error.
Error Number = 170221
Unknown ADO item type: <146>
Has anyone a suggestion for me? This is exceedingly frustrating – WINDEV promises a tenfold productivity increase but this is taking me days, simply to try and get existing tables into a WINDEV analysis.
The last point on this is that PC Soft support keep insisting I must try the Native connection. I asked the following question in that regard:
"The problem is that I must first purchase it, before I know that it works. Why can I not get a free version to develop with, and then pay for it when implemented on the customer’s server? I cannot just buy something without knowing that it will work, and I should not have to buy something just because WinDev does not work with the other connections."
The answer I received is the following, which seems to imply that I ask other developers for a copy of the native access driver?
Hi Guy,
I fully understand your need to be assured it's working. There is an easy way to do that and it will not cost you a dime.
You simply have to ask other developers on the forum.
https://forum.pcsoft.fr/fr-FR/pcsoft.us.windev/page/1.awp
We wish you great success developing with our products. |
| |
| |
| | | |
|
| | | | |
| | |
|