Hi Ginny,
I don't know what this group would do without you :) I believe the SQL
Compact Edition version used on the mobile devices was 3.1, however,
my desktop is using 3.5. The work around I am now using is to
configure my desktop app to use the 3.1 SQL CE libraries as well. I
have experienced no problems since making the switch; however, I still
think that SqlCeException message I received should probably be
investigated by an MS dev.
The full write-up and workaround is posted here:
http://csharponphone.blogspot.com/2008/07/sqlceengineupgrade-causes.html
Jon
On Jul 6, 9:26 pm, "Ginny Caughey MVP"
<ginny.caughey.onl...@wasteworks.com> wrote:
> Jon,
>
[quoted text clipped - 89 lines]
> > ----
> >http://csharponphone.blogspot.com
Ginny Caughey MVP - 07 Jul 2008 12:27 GMT
Thanks for the follow up, Jon. I'll make sure the team is aware of the
message if that's still what happens with 3.5 sp1 beta - I haven't tried it
yet.
Ginny
Hi Ginny,
I don't know what this group would do without you :) I believe the SQL
Compact Edition version used on the mobile devices was 3.1, however,
my desktop is using 3.5. The work around I am now using is to
configure my desktop app to use the 3.1 SQL CE libraries as well. I
have experienced no problems since making the switch; however, I still
think that SqlCeException message I received should probably be
investigated by an MS dev.
The full write-up and workaround is posted here:
http://csharponphone.blogspot.com/2008/07/sqlceengineupgrade-causes.html
Jon
On Jul 6, 9:26 pm, "Ginny Caughey MVP"
<ginny.caughey.onl...@wasteworks.com> wrote:
> Jon,
>
[quoted text clipped - 94 lines]
> > ----
> >http://csharponphone.blogspot.com
Ginny Caughey MVP - 07 Jul 2008 18:39 GMT
Jon,
This code behaves as expected with a SQL Compact 3.1 database for me with
whatever 3.5 sp1 beta I have on my machine:
string pathToDatabase = @"Data source=c:\tickets.sdf";
SqlCeConnection sqlConnection = new SqlCeConnection(pathToDatabase);
try
{
sqlConnection.Open();
}
catch (SqlCeInvalidDatabaseFormatException eSql)
{
SqlCeEngine sqlCeEngine = new SqlCeEngine(pathToDatabase);
string newPathToDatabase = @"Data source=c:\tickets35.sdf";
sqlCeEngine.Upgrade(newPathToDatabase);
sqlConnection = new SqlCeConnection(newPathToDatabase);
sqlConnection.Open();
sqlConnection.Close();
}
Ginny
Hi Ginny,
I don't know what this group would do without you :) I believe the SQL
Compact Edition version used on the mobile devices was 3.1, however,
my desktop is using 3.5. The work around I am now using is to
configure my desktop app to use the 3.1 SQL CE libraries as well. I
have experienced no problems since making the switch; however, I still
think that SqlCeException message I received should probably be
investigated by an MS dev.
The full write-up and workaround is posted here:
http://csharponphone.blogspot.com/2008/07/sqlceengineupgrade-causes.html
Jon
On Jul 6, 9:26 pm, "Ginny Caughey MVP"
<ginny.caughey.onl...@wasteworks.com> wrote:
> Jon,
>
[quoted text clipped - 94 lines]
> > ----
> >http://csharponphone.blogspot.com
Laxmi Narsimha Rao ORUGANTI [MSFT] - 11 Jul 2008 17:16 GMT
Hey Ginny and Jon,
I am a developer in SQL Server Compact Team and we definitely want to look
at this issue in much deeper. Though I can not guarrenty I can get a fix
for you in v3.5 SP1 RTM (It is internally went to RTM already); it would
still be important for us to find the root cause. Once we confirm that
there is indeed a bug in the code, you can get the fix by going thru normal
support channel if required (free of cost).
Can you please contact us thru the blogs:
http://blogs.msdn.com/sqlservercompact/contact.aspx OR
http://blogs.msdn.com/laxmi/contact.aspx
Thanks,
Laxmi [Disclaimer: All postings are as-is and confer no rights]
> Jon,
>
[quoted text clipped - 135 lines]
>> > ----
>> >http://csharponphone.blogspot.com
Ginny Caughey MVP - 11 Jul 2008 17:59 GMT
Thanks, Laxmi. Good to hear! Do you need a repro case? I'm not seeing with
with 3.5 sp1 beta.
Ginny
> Hey Ginny and Jon,
>
[quoted text clipped - 152 lines]
>>> > ----
>>> >http://csharponphone.blogspot.com
Laxmi Narsimha Rao ORUGANTI [MSFT] - 11 Jul 2008 18:11 GMT
Jon seems to have reproduced it with a particular database. So it is highly
likely that you are not able to reproduce the same issue with your set of
databases. I want to get hold of that particular database to really see
which combination of on-disk pages causes this issue. If you happen to have
got the copy please post it.
Thanks,
Laxmi [Disclaimer: All postings are as-is and confer no rights]
> Thanks, Laxmi. Good to hear! Do you need a repro case? I'm not seeing with
> with 3.5 sp1 beta.
[quoted text clipped - 159 lines]
>>>> > ----
>>>> >http://csharponphone.blogspot.com