This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I'm having a problem getting Lightspeed to connect to my model using lInqpad. I rebuilt my (WPF/C#) project ticking 'make COM visable', and then used the 'Infer' option, pointing it at my exe (there is no dll created), this seemed to work as my tables appeared on the right. Whenever I run a query I get an error. Initially the complaint was that the CE4 dll was not available, I copied this into my debug\bin folder and I now get a different error: The database file may be corrupted. Run the repair utility to check the database file. [ Database name = C:\Users\Darren\Dropbox\Incubate\Notebud\dev... There isn't, but I ran repair anyway, same deal. Am I configuring it incorrectly? I'm using a very recent nightly build of Lightspeed and the newest beta of Linqpad (I tried this after using the stable version first having the same problem) I've attached a screengrab of the linqpad properties screen. Thanks in advance. |
|
|
Try using this updated LINQPad driver. Let us know if the issue continues after updating.
|
|
|
Thanks for this. It's not asking for SQL server anymore, instead I get: Method not found: 'System.String Mindscape.LightSpeed.Properties.Resources.get_DBNoPaging()'. I am 'using' Mindscape.LightSpeed.Providers.VistaDB4 Mindscape.LightSpeed.Linq Mindscape.LightSpeed and the dlls exist in the output folder. |
|
|
Thanks for reporting this, looks like that resource string has been stripped by our obfuscation process so Ill get that resolved. The error you are seeing however is due to paging not being supported by VistaDB so you will need to remove any .Skip() call in your LINQ query to cover this.
|
|
|
AH, OK, I was simply running one of the default queries when one right clicks on a table. e.g. tableName.Take(100) which I guess does use paging. I can confirm that that a standard query such as from n in TableName select n does work. Thanks |
|