Ahh, schemas. We don't run into that often but here's what you might try.

When you generate your code if you make sure to have the ignore schema/catalog checkboxes checked then your user id you use in your connection should have access to the right table, but still, I think there would be issues. How do you plan to indicated what schema to use (I usually avoid schemas but that's another issue).

Ha ! You just made me think of something, try this:

col_fact.Query.es.QuerySource = "mayorpit.factura";

Then do everything else as normal.

This should get the same "Invalid object name" in Management Studio as it does from the app:

SELECT * FROM [MAYORPIT.FACTURA]

Assuming the "Initial Catalog" is set to the database in your connection string, the correct syntax for schema and table is:

SELECT * FROM [MAYORPIT].[FACTURA]

To accomplish this in EntitySpaces, regenerate your Generated Master. Check "Use Custom Base Class" on the advanced tab. Add the three files in this folder to your VS project:

C:\Program Files\EntitySpaces 2008\CodeGeneration\CustomBase\C#

Open CollectionBase.cs and add this method:

public void SetSchema(string schemaName)
{
    esProviderSpecificMetadata spec = 
        this.Meta.GetProviderMetadata("esDefault");
    spec.Schema = schemaName;
}

Usage examples based on AdventureWorks:

EmployeeCollection emps = new EmployeeCollection();
emps.SetSchema("HumanResources");
emps.LoadAll();

CustomerCollection custs = new CustomerCollection();
custs.SetSchema("Sales");
custs.LoadAll();