I am on VFP 5.0. > I am wondering if anybody knows the derivation of this > message and can point me in a direction towards solving > this problem. > Saturday, April 20, 2013 8:53 PM Reply | Quote Moderator Microsoft is conducting an online survey to understand your opinion of the Msdn Web site. but occassionaly only. The server is running MS Small Business Server 2003. get redirected here
OK, if really nothing changed in your system,1103 means invalid pointer in index file (if I remember it well)did you reindex all tables? This is not the same thing as a legacy application being continually open over a mapped network drive and dragging hundreds of megabytes across the network connection from multiple shared data Good luck, this one can be a bear. - William Fields ISO error means that there is index corruption, likely caused by those network disconnects. I could give you the entire log entry when the ISO causes the program to crash - maybe something in there could set off a light-bulb somewhere out there?
The reason I think it's NOT the physical index is that when it fails with the 1103 - all we have to do is stop the program, restart it Anyway - Legacy applications have no way of interacting with Windows to provide stability in a network situation–they expect the data to be there on a particular drive letter and if it isn’t The client computers are running Windows XP.
Several functions may not work. Visit our UserVoice Page to submit and vote on ideas! Stable network having proper setup should also be OK. Network Servers Preparing Workstations Topic New Topic Reply to Topic Printer Friendly Jump To: Select Forum TriForce General Discussion New Features FAQ Software Issues LiveUpdate / Updating TriForce Hardware/
The reason for the term "predictive" is - the dialer will speed up / slow down (dial more / fewer calls) as it attempts to predict what it will take to I need to use the Windows Task Manager to end the VFP9 process. Part of the cause seems to be somewhat frequent disconnects from the network, which we are addressing, but is there a way to make the FoxPro app react to these problems http://www.tek-tips.com/viewthread.cfm?qid=1146115 Date and Time: 4/11/2013 12:01:27 PM Error number: 1103 Error message: Invalid seek offset.
Virginia Win7 Professional x64 Back to top #3 Jim Byram Jim Byram Moderators 7,163 posts Gender:Male Location:Framingham, MA Posted 11 August 2010 - 07:27 AM It's not an error that we're from the server to the workstation and then back to the server. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. It means the line of code and data used to generate the bug.
By the way - I spoke to the former CEO of the dialer company - his suggestion also lied with Anti-virus - he suggested that I take a clean, recently re-imaged Of course, I cannot trap this error so I do not know what line of code may be triggering the error. mabe this can be a way to explore??Martin RE: Invalid seek offset (Error 1103) DSummZZZ (Programmer) 2 Nov 05 17:06 Quote:I replace all data with fresh new database/tables/indexBut did you recreate Date and Time: 4/19/2013 12:01:41 PM Error number: 1103 Error message: Invalid seek offset.
copy a folder with 100mb of data . Get More Info The help >file says to gather all information about what was running >and call Microsoft. Sitemap Thanks for your registration, follow us on our social networks to keep up-to-date Home Information About TriForce XP Why TriForce XP Solutions Literature System Requirements Live Update Testimonials Contact Us Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free.
Click Here to join Tek-Tips and talk with other members! The many combinations of network Operating System, client Operating Systems, and network hardware provide many opportunities for problems to occur. I'll check the rest of the scheduled tasks, Windows logs, etc and reply (see my reply above). useful reference Invalid Seek Offset (error 1103) 2.
Graeme Evans (www.Adminsoft.com) Mar 29, 2010. --- We triggered Invalid Seek Offset Error 1103 when trying to process a 7GB file on NTFS hard drive using VFP 9 that had been It is an on-line > application which users connect to via Citrix. We have 100 users connected concurrently every day via VFP COM components and we are not even doing reindex every night...
What I find is important for your customer to understand is Office is usually installed locally on workstations and its only involvement with the network is to open the occasional 30Kb VFP indexes are not 100% bug free and you should also save all conditions when the error happens. Thanks for the feedback...DavidDavid Saturday, April 20, 2013 8:26 PM Reply | Quote 0 Sign in to vote Based on the fact you are reindexing every nightit seems the problem is Invalid Seek offset - error 6.
We fight this much less now with VFP9 SP2. Create new indexes using the INDEX command. Date and Time: 4/10/2013 12:01:58 PM Error number: 1103 Error message: Invalid seek offset. this page Is a windows backup enough to be able to recover from?
Invalid Seek Offset Error Message Occuring 8. Do these problems have anything to do with the fact that I am mapping to the executable rather than running a copy of the executable local on each client pc?