Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem running VFP8 and ActiveSync at same time

Status
Not open for further replies.

TonyScarpelli

Programmer
Jan 23, 2003
361
US
I am having a problem running VFP8 SP1 and ActiveSync 7.1 at the same time under Windows NT.

I keep on getting a VFP8.exe Application error. It says
"The instruction at "0x660d5934" referenced memory at "0x00000034". The memory cound not be "read".

Sounds like FP is trying to access the same memory as ActiveSync.

I am starting VFP8 with a config.fpw file that has a
MEMLIMIT=20,3072,4096.

Any ideas on this one?

Thanks.


Tony Scarpelli
Clinical Engineering Dept.
Maine Medical Center
Portland, Maine 04102
 
Tony,
Is that Microsoft's ActiveSync for Pocket PCs (and other Mobile Devices)? My version is 3.7.1, and I've run it with VFP 6.0 SP5, 8.0 SP1 and 9.0 (Beta) on XP without any problems. Are you running NT with SP6a?

Rick
 
What is it that is leading you to believe ActiveSync is causing grief with VFP?
I don't have VFP 8 installed but I've done quite a bit of testing reading and writing on a Pocket PC device using VFP 7 with no issues other than lack of Pocket PC experience getting in the way.


-Dave Summers-
[cheers]
Even more Fox stuff at:
 
If I have Microsoft ActiveSync 7.1 running, and a Compaq 3650 Pocket-PC connected to my computer via a serial port on my NT SP4 machine, or via a USB port with an HP h2200 PPC on my win 2k machine, I get the same error whenever I open up a screen under VFP 8 SP1.

I can start the project, but it only occurs when open a screen.

If I close ActiveSync and turn off or disconnect the PPC's, the error doesn't occur.

Seems like a link between the two.

Thanks.

Tony Scarpelli
Clinical Engineering Dept.
Maine Medical Center
Portland, Maine 04102
 
Tony,
Have you considered upgrading NT to SP6a? While no version of NT 4.0 is officially supported for VFP 8.0 (or 9.0!) - at least an update that was released more than 3 years ago is more likely to be compatible with VFP 8.0.

Is the Win 2000 machine on SP2 or higher?

Rick
 
According to MS, to run ActiveSync 3.0 / 3.1 / 3.5 / 3.6 / 3.7+, you need Windows NT 4.0 SP6a and MSIE 4.01 SP1 or above.
As Rick said, it looks like you need to start with the SP6 install.
Let us know how it turns out please.


-Dave Summers-
[cheers]
Even more Fox stuff at:
 
Our IS guys have been updating our operating systems pretty regularly to the latest versions. SP6 for NT, and SP4 for Win 2K. I don't think that is the problem, though, because my Win 2K machine does the same thing as the Win NT machine.

There might be something else going on, but I couldn't check what I'm thinking, I've been running around all day on another problem, today was just chaotic.

The IS guys just updated us last week to the latest Novell Client and one of my FPW 2.6 apps won't run at all. It won't even find the application. It's been working for two years, and now they broke it.

We are in the process of updating all our workstations to Win 2K and then to Win XP, so at least that won't be in the mix any more. They take a couple weeks to get it into the que.

I'll let you all know what I find out.

CU


Tony Scarpelli
Clinical Engineering Dept.
Maine Medical Center
Portland, Maine 04102
 
I think I have the problem solved.

I have an ActiveX control on my screens called CeSyncAX. It allows me to copy, move, delete, etc. files from a Pocket-PC to the PC and vice versa without using the Pocket-PC's "\My Documents" sync directory.

Since the project and screens were old ones that I was reviving they had references to an older version of the control. So when I opened a screen with the control on it I would get an application error. The control also needs ActiveSync to be the connector between the two devices.

If ActiveSync wasn't used I was able to open the screen, but when it was used, I got the error.

Happens that there was an updated version of the control available at the web site where I got the control.

After installing the new version, the problem went away.

Whew.

Hope this helps someone out there.

CU


Tony Scarpelli
Clinical Engineering Dept.
Maine Medical Center
Portland, Maine 04102
 
Don't take me wrong here, but you left out a couple important pieces of the puzzle!
I don't think either of us (Rick or I) realized you were using VFP and an ActiveX control to communicate through ActiveSync to a Pocket PC. Personally, I was thinking you just had VFP running on a system along with ActiveSync.
In the future, you should elaborate a little more on what you are doing, and include any 3rd party components you are using to build your apps.
Again, I don't want to sound crass, but that may have helped in the sloution discovery.


-Dave Summers-
[cheers]
Even more Fox stuff at:
 
Bob, I got the control from
It's works very well since you can also move FoxPro tables back and forth from and to the Pocket-PC without using the sync directory. It becomes an Access table on the Pocket-PC.

Dave, I did mention I was using VFP 8 SP1 and ActiveSync 3.7 in my first message.

I also haven't opened this project in over a year when my main programming machine was a Windows NT machine.

Also, since the error message was a "VFP8.exe Application" error it didn't even occur to me that a control on the screen could have done this, expecially since there was no error when I wasn't using ActiveSync, and I'm not a real expert with these ActiveX types of controls. The connection in my mind was VFP8 and ActiveSync, not the control at all. I didn't get the connection to this control at all until I brought the project home and had to work on it there, for many, many minutes, I might add. I'm 62 years old and I know my mind isn't as fast as you young whipper-snappers, but eventually I figured it out.

But thanks for your help anyway.

CU




Tony Scarpelli
Clinical Engineering Dept.
Maine Medical Center
Portland, Maine 04102
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top