Search results for query: *

Gah! That was it. Switching between VFP, VBA and C# I get confused sometimes! Thanks MakteItSo. *************************************** Need help running those old FoxPro apps on modern systems? http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

I've got code along these lines: <snip> function DoImport() Dim oCompanyRS As ADODB.Recordset Set oCompanyRS = GetCompanyList("c:\folder\system") end function Function GetCompanyList(FullSystemPath As String) As ADODB.Recordset cConnectString = "Provider=VFPOLEDB.1;Data...

If you're using HP PCL6 drivers try using a standard LaserJet 4 driver instead, or the PCL5 versions. *************************************** Need help running those old FoxPro apps on modern systems? http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

Try putting: stacks = 10,256 in your CONFIG.SYS under 95/98 or CONFIG.NT under 2K/XP *************************************** Need help running those old FoxPro apps on modern systems? http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

There are third-party applications which let you do it. The easiest way is to share it from the server as so then you can NET USE an LPT port to say \\server\usbprinter and then print to the LPT port from your FPD app. *************************************** Need help running those old FoxPro...

He means do a SHOW GETS. You can't do what you're trying to do without stuffing the keyboard buffer. *************************************** Need help running those old FoxPro apps on modern systems? http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

Sorry that should have been: PC1 NET USE LPT1 \\PC2\PRINTER PC2 NET USE LPT1 \\PC1\PRINTER *************************************** Need help running those old FoxPro apps on modern systems? http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

Well it's a good idea to NET USE above LPT2 in case there's ever a physical printer on LPT1 on a particular PC. I don't see how redirecting LPT1 on a PC to a shared printer on another PC would create an endless loop though. PC1 NET USE LPT1 \\PC2\PRINTER PC2 NET USE LPT2 \\PC1\PRINTER So if...

Under FPW / FPD .... forget it. Sorry! *************************************** Need help running those old FoxPro apps on modern systems? http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

Under ME you need to edit SYSTEM.INI and change or add the PerVMFiles setting, 200 should do it. *************************************** Need help running those old FoxPro apps on modern systems? http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

The best approach under NT/2000/XP is to use a NET USE command in Windows to redirect an LPT port to your shared printer, then print to LPT whatever in your app. The method you had is flaky IMO - may work on some setups, doesn't on others. NET USE LPT3 \\server\sharedprinter Then SET PRINTER...

Make sure you're running at minimum 800x600 desktop with Small Fonts too. If you're doing any @ ... SAY commands or the like make sure the co-ordinates you're specifying are inside the bounds of their window. *************************************** Need help running those old FoxPro apps on...

You're talking about FoxPro 2.6 for DOS / Windows, not VFP here ? You can't AFAIK. Sorry! It might be better to put the data into a cursor instead. Like: SELECT field1 + &quot;|&quot; + field2 FROM table INTO CURSOR temp Then base the list on the cursor - you'll see 2 columns in the list...

Looks OK, although you'll probably get a nasty command prompt window flashing onto the screen! *************************************** Need help running those old FoxPro apps on modern systems? http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

No, TameDOS just addresses a problem where DOS apps continually poll the keyboard and cause 100% CPU utilization. I think the only 100% foolproof solution is to use NET USE commands in Windows and then just print to the relevant LPT in your app, i.e. SET PRINTER TO LPT2. You have up to 9 which...

The keyboard thing is the usual - many DOS apps including FoxPro for DOS continually poll the keyboard, resulting in high CPU usage and sluggish performance under NT-based operating systems. You can look at things like www.tamedos.com to alleviate that. Regarding the blinking ... try different...

NTFS isn't a problem ... like rqbean said, DOS / Win16 apps run in an emulated machine under Windows 2000, so you're well isolated from the OS file system. I'd have to query the statement that FPD and FPW can't use mor e than 16Mb memory though! Also, this article may be helpful...

No ... you can't cheat like that! :) You may need to look at how your data is organised. *************************************** Need help running those old FoxPro apps on modern systems? http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

Ok, say you have name (30 chars) age (numeric, no decimals) salary (numeric, 12 long with 2 decimals) date of birth (date) other details (memo) then you might use: create table mytable (name C(30), age N(3,0), salary N(12,2), dob D, other M) *************************************** Need...

FPD (and other DOS Apps) can cause heavy CPU utilisation under the NT kernel operating systems, i.e. NT, 2000, XP. This is due in a large part to their continual keyboard polling. I find the best solution is TameDOS from Tame Software. You can also alleviate it by setting CLOCK=OFF in CONFIG.FP...