POCKET PC 2003 and Windows Mobile 6 Pro BIG issue

  • Thread starter Thread starter LAF
  • Start date Start date
L

LAF

We created a proyect for symbol PPt8800 devices, now we bought the MC75, and
we want to install the proyect in the new device so we update to SQL2005 wit

We are using SQL 2005 and SQL Mobile 2005, but every time we try to install
the proyect we have an error with the sql dll. We don't know what to do.

Is there something special we need to modify to run the proyect in the new
mc75?
We must install the app on both kind of the devices. Any idea?

Thanks
 
Hi,

LAF said:
Is there something special we need to modify to run the proyect in the
new
mc75?
Click to expand...

There shouldn't be anything specific that you need to do for the new device.

One thing you might like to try (if you haven't already) is to use the SQL
Server CE CAB files that are most relevant for your new device (probably
sqlce.ppc.wce5.armv4i.CAB). I assume at present that you have been
installing the same cab you used on your older PPC2003 device?

Are you able to explain the error message you are seeing? That may help get
you a more specific solution.

Hope this helps,
Christopher Fairbairn
 
Hello Christopher , thank for your answer.
The error said "Can't find PInvoke DLL 'sqlceme35.dll' "

We did what you said, we executed 3 cabs located at program files/MS SQL
Compact Ed/v3.5/Devices/wce500/Armv4i directly on the MC75, after that we
could install the program with no errors. We don't really know the
differences between wce400, wce500 (armv4i, mipsii, mipsii_fp,x86).

The program is now running, even the forms of the program fit the screen of
the MC75, the controls don't. They look narrow and they go to one corner, is
there a way to change the size of the controls according to the size of the
screen (resolution)?

Thanks a lot for your time and help.

REGARDS.





I installed the 3 cabs
 
Your starting point will be to set the following in the constructor for each
of your forms:

this.AutoScaleDimensions = new System.Drawing.SizeF(96F, 96F);
this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Dpi;

Then google for MSDN AutoScaleMode

BUT, I have recently ported an application from an MC70 to an MC75 and I
have to warn you that the implementation of AutoScaling isn't perfect and
results in some strange control sizes once you start to use inheritence in
your form construction and reference the control metrics in your base forms
outside of the derived forms constructor. I have yet to determine a pattern
to what happens, but am sure there must be one.

Paul K
 
Hello Paul,

The code is working, now we have to figure out how to resize the controls
(textbox, labels, etc) because they didn't resize.

At first we tough the code didn't work because for some reason every time we
modified the code and sent the proyect to the mc75 it didn't update the
exe; MC75 was executing the old exe, after we noticed that we erase the old
exe to make sure and we reinstalled it again.

Thanks a lot for your help!
 
Back
Top