Discussion Groups

Bill

Are you implying that I have to use C++ to use PsionTeklogixCE500

No.  You do not need to use C++ at all.  What I'm saying is that the 'PsionTeklogixCE500' option is a target option ONLY for C++ environments.  You are developing in VB, and thus you do not need to worry about this option (or the lack thereof).  Merely select the compact framework level that you want, and continue on.

OK I am good to go with VB Form1 compact framework 3.5 etc...

1) Now I have to learn about developing with visual studio again ( it has been years )

AND

How do I get the RFID scanner to work with my application

Bill

Never mind that last question re the scanner.

I got this:

http://community.psionteklogix.com/cfs-file.ashx/__key/CommunityServer-Wikis-Components-Files/00-00-00-00-15/3660.Partner-_2D00_-Agrident-_2D00_-AIR200.zip

And I think I am off to the races as they say. Thanks for the help.

Bill

Bill.

Let us know when you get to Agrident Reading of tags etc.  The Keyboard wedge works good too.

Another note to make is :The Agrident RFID cannot "write" to transponders. (tags)  This is a limitation of the Agrident device, and other RFID solutions are available to take care of Custom Data written to transponders.

-sean

You say the keyboard wedge is good. It sounds like I would like that too for my applications if I am interpreting the idea correctly.
How would I set that up for mu unit and VB. Is there an example somewhere?

I do not believe that I will ever need to write to the RFID tag.

Bill

Hi Bill.

The Keyboard Wedge is a default operation: If there is a TextBox that has the Caret (Cursor) within it, then an RFID scan will inject the data into that TextBox.

Or, you can make your app event based, and with that any scan from the RFID will show up as an event, and you can process it.

Keyboard wedge however is simpler and works on Web-Based TextBox interfaces too.  

There is a Demo sample project that VS2K8 will likely attempt to upgrade: I suggest making a copy of this project from the folder found here:

"\3660.Partner - Agrident - AIR200\Software tools\AIR_Software+SDK_for_CF2\WM5_WM6_WCE5\AirSDK\examples\VB\"

And then allow VS2K to upgrade that copy, and keep the original in case something messes up...

 -sean

Is there something special you need to do to make air wedge work?
Remember I had to do a factory reset.

Anyway I launch wordpad then press the scan button with a tab that works with my application and nothing shows up.

I will likely do it event based but I would also like the fundamental air wedge to work too.

Bill

Hi Bill.

If you installed AirWedge, then you need to start AirWedge and configure it to get an F-key that you can can assign to a Scan Code remap.

I set it to use F10, or F20 to use the [BLUE] <zero> or a [BLUE] <L>  on a WAP and that allows a Keyboard trigger.

Then you can use scan code remap to set it to a trigger button.  Search for one of my postings (or Luke's postings -- his have pictures) about Scan Code remap.

If you use the Sample App, than you don't need to, but the RFID reader will likewise be unavailable to any other apps since AirWedge would not be running.

-sean

I am now starting to develop using VB

According to the specs for the workabout pro 3 it is Full VGA 480 x 640 resolution

So I made a form that size for windows CE and it is way too big.

What should the size of my main form be?

Bill

Hi Bill

On Workabout Pro 3, Windows CE is QVGA rather then Portrait VGA.

Windows Mobile is VGA dimensions.

You can try 160 x 240 for the form on Windows CE.

-sean

Bill,

Although our Workabout Pro G2 and WORKABOUT PRO 3 come with a full VGA screen (480x640), devices running CE 5.0 are by default configured into 1/4 VGA (240x320) mode.

This said, in case it helps, let me bring the « How to change screen size to Full VGA on Windows CE 5.0 - How To? » knowledge base article to your attention.

Kind regards.
Jacques

Thank you.

I have a basic VB-CE application running now and I think I will exist in the usual screen size.

My project would roughly be as follows:
1) The user will need to transmit some data into my  workabout-pro app taken from a huge database.
2) S/he then takes the unit to the field and collects more data by reading an RFID which focuses on a record.
3) Then the user may add to the record either with the keyboard or tapping on the screen or even in the future by blue-tooth reading data from a measurement device.
4) Finally the user returns to home base and uploads the new information to the main database.

That probably seems like what most applications for the workabout-pro do.

If any of you could offer advice or point out some specific articles in the knowledge base etc that may help me I would appreciate it. I will be using my new installation of visual studio 2008 VB.net for win CE.

Bill

Well...

Dropping my Calculator aside -- Since I screwed up my Calc for the QVGA... (Thanks Jacques...)  I think a good start may be as follows:

Bill: Take a look at the SQL sample I posted here:  http://community.psion.com/downloads/developer_sdkhdk/m/sample__demo_code/34598.aspx

For two reasons.  A) It contains SQL client side code that uses TCP/IP networking to attach to the SQL back-end.  B) It writes data to Flat files.

Doing the exercise in reverse I leave to you: It is doable. Using ActiveSync for debug is fine, but set Activesync up to act as a connection to "The Internet" so that the HHT device can connect to the SQL server.  (And don't run the SQL server on your Dev Box running the Debug! Run it on another PC on the network!, This is important when you migrate to Real-World situations.) Reading from TXT Files should be straighforward.

The REAL Exercise is envisioning the best method to get the data back onto the back end. Think of this FIRST!  I blogged a bit about this already, but since you are starting with a good idea in your head (Rather a good Development Pattern really.) I urge you to think of this as the primary goal, and the rest of the design as making License Plates. (Boring, Needed to be done, and lot of it done before already by many others.)

Here is my suggestion : I come from the MySQL side of Database development; and One Feature I enjoyed the most was that the BACKUPS for MySQL were in huge Text Files!  All of it with SQL statements for repopulating and re-generating pretty much EVERYTHING in the Database.

Every table, for every row, containing a SQL statement to re-populate.  

In your case, if there are update transactions that need to be committed to the database,  -- Make it a SQL statement in your Update file.

If there are add-record entries.  Use SQL statements to ADD Rows. You get the picture.

This allows for two things to occur.  1) SQL statements are veiwable and re-viewable.  A DBA can look at the SQL and know intimately what to do with them. 2) Data Recovery.  If the HHT fails, and the data was written as transactions to a SQL file on the "\Flash Disk\" or "\SD-MMC Card\", it is likely recoverable so long as the "\Flash Disk\" or "\SD-MMC Card\" is not erased if a HHT has a .CLEAN boot, or of the device suffers a failure.  ("\SD-MMC Card\" is handy too, since it can be removed from the device and accessed using a PC.)

There are other demo's too, download them and take a look. If you like something, -- Use It!            -sean

Thanks for that Sean.

I have a couple more questions.

1) If I simply wanted to use an access database in the workabout would I need the sql server?

2) I do really want to use the SQL server and yes my main database is mysql but I am having the following error when trying to install another application that someone else wrote for this workabout. Error ---> can't find pinvoke dll 'sqlceme30.dll'
I think it is because way back we did a "back to factiry settings: and some files got removed.
Where can I get the appropriate files and where do I put them in my device?

Bill

Hi Bill.

MS-SQL == Yes.    (Fact of life today, but that's not a bad thing.)

Since Access (MS-JET) is a non-network database platform that also is x86 only, I usually suggest migrating MS-ACCESS projects to MS-SQL, and refactor the interface client in VB.NET.  This is not easy, simple, or not frought with peril, but the migration is an excellent way to understand how to build the client on the HHT side.

Good to hear that you got MySQL as a back end. Trouble is, there is no MySQL clients for ARM-Based Windows Terminals. There is SQL CE 3.5 for Windows Terminals, and that requires an MS-SQL back end.  Do a Search on Microsoft.com for SQLCE 3.5  and you will find the downloads you are looking for.  (The SQL Client software that the demo code relies upon is the "sql.wce5.armv4i.CAB" installer for the device.)

Hope this helps a bit.  -sean