ODBC (SQL SERVER 2012) de 64 bits y ODBC(SQL SERVER 2012) de 32 bits....

[rodribezul]

Hola al establecer conexion con ODBC (SQL SERVER 2012) de 64 bits me generar error y al conectarse por ODBC de 32 bits me genera el siguiente mensaje :ODBC connection to focus successful
Importing from ODBC connection 'focus' into local database ''
7 tables to import
Importing table 'dbo.MSreplication_options'
Importing 3 records...
3 records imported successfully in 105 ms
Importing table 'dbo.spt_fallback_db'
Importing 0 records...
0 records imported successfully in 44 ms
Importing table 'dbo.spt_fallback_dev'
Importing 0 records...
0 records imported successfully in 53 ms
Importing table 'dbo.spt_fallback_usg'
Importing 0 records...
0 records imported successfully in 72 ms
Importing table 'dbo.spt_monitor'
Importing 1 records...
1 records imported successfully in 124 ms
Importing table 'trace_xe_action_map'
** Error 208 **
[Microsoft][SQL Server Native Client 11.0][SQL Server]El nombre de objeto 'trace_xe_action_map' no es válido. Importing table 'trace_xe_event_map'
** Error 208 **
[Microsoft][SQL Server Native Client 11.0][SQL Server]El nombre de objeto 'trace_xe_event_map' no es válido. ODBC database import operation completed with errors

[barrymavin]

Are you using user defined columns? These cannot be mapped into any other database as they are MSSQL server specific and are non standard.

[rodribezul]

I'm just asking for odbc Connection is using the option in app builder lianja \ data \ import odbc database

[barrymavin]

Hola Rodrigo,

Yes I understand. Let me see table structure with data types for "trace_xe_action_map".

[yvonne.milne]

Possibly also related to the current user / database owner not being the owner of the table:

http://technet.microsoft.com/en-us/l...v=SQL.80).aspx
http://technet.microsoft.com/en-us/l.../cc280443.aspx

[rodribezul]

the user is 'sa' and work fine from visual foxpro 9.0

[barrymavin]

Ok that may well be so but in order to identify the issue that you are having I need to see the structure of that particular table. Let me see that then we can move on to resolve it.

[barrymavin]

If you type this in the console:

SET DEBUG ON

Then go and import the MSSQL database again, when it fails attach the file c:\lianja\debug\debug_client.txt to your ticket. That will help us track down the problem.

[rodribezul]

[barrymavin]

Hola Rodrigo,

Please follow these instructions then submit a ticket with the contents of c:\lianja\debug\debug_client.txt so that we can investigate this.

In the console:

SET DEBUG ON

Then import your MSSQL database.

When it crashes please submit the debug_client.txt file as a ticket at Submit a Ticket.