Problems with LinqConnect

markw · Post by **markw** » Tue 11 Oct 2011 03:17

I am trying to connect to an Oracle database using LinqConnect. After I choose the tables I want in my model I get an error “A method called Insert_record already exists. Please choose a different name.” This is a show stopper as the wizard does not complete the process and create the model.

I need some help urgently!

StanislavK · Post by **StanislavK** » Tue 11 Oct 2011 08:47

This error occurs on an attempt to add a method with the same name as one of methods already available in the model. If this is done automatically (e.g., the method is added by a wizard), however, Entity Developer should implicitly change the name of the second method.

Could you please specify the following, so that we are able to analyze the issue in more details:
- the version of LinqConnect (or dotConnect for Oracle) you are using;
- the exact scenario you are trying to perform when the issue occurs (e.g., you create the model via a wizard, or drop the tables from the Database Explorer tool window).
If possible, please specify the script needed to create the database objects and/or send us the model with which the issue occurs.

I've deleted your duplicate post.

markw · Post by **markw** » Tue 11 Oct 2011 23:37

I am using LinqConnect Professional version 3.0. This problem also occured with the previous version. The problem occurs when I use the wizard to create the model.

Where should I send the model?

StanislavK · Post by **StanislavK** » Wed 12 Oct 2011 10:32

Please use our contact form:
http://www.devart.com/company/contact.html
or send the model to support*devart*com (replace the asterisks with '@' and a dot).

markw · Post by **markw** » Wed 12 Oct 2011 12:21

I sent a mail to [email protected] with project directory and screen sht of error received.

StanislavK · Post by **StanislavK** » Thu 13 Oct 2011 13:50

Thank you for your assistance, we have reproduced the issue. Apparently, it occurs when adding two methods that have the same name, but are declared in different packages. We will analyze the issue and inform you about the results as soon as possible.

As a temporary workaround, you can open the .lqml file in a test editor and manually rename the methods with duplicate names.

Eg., replace the entries like

Code: Select all

with

Code: Select all

Please tell us if this helps.

markw · Post by **markw** » Tue 18 Oct 2011 20:05

I tried renaming the lqml file but am unclear as to what to do next. When I recompile and try to use the model I find it is not available.

What can I do? Does the new release of LinqConnect deal with my problem?

markw · Post by **markw** » Tue 18 Oct 2011 20:07

I tried renaming the methods in the lqml file. When I recompile and try to use the model I find it is not available. I am unclear as to what to do next.
What can I do? Does the new release of LinqConnect deal with my problem?

StanislavK · Post by **StanislavK** » Wed 19 Oct 2011 11:39

Could you please specify what exactly you mean saying that the model is not available (e.g., the code is not re-generated, or you encounter an exception when trying to create a context)? The proper steps are:
- to change the method names in the .lqml file in a text editor;
- save this file and open it via Entity Developer;
- re-generate the model code;
- launch your application.

We are still working on this issue, we will post here when it is fixed.

StanislavK · Post by **StanislavK** » Thu 17 Nov 2011 08:40

The issue with creating methods having the same name is fixed. The fix is available in the latest 3.0.14 build of LinqConnect.

The new build can be downloaded from
http://www.devart.com/linqconnect/download.html
(the trial and free versions) or from Registered Users' Area (for users with active subscription only).

For the detailed information about the fixes and improvements available in LinqConnect 3.0.14, please refer to
http://www.devart.com/forums/viewtopic.php?t=22548