colin_e wrote:
> $Bill Luebkert wrote:
>
>>
>>
>>That's because you didn't close $command before trying to delete
>>the temp files. DIR still has them open for write and unlike
>>UNIX, Doze can't delete files that are in use.
>>
>>
>>
> Thx Bill. (also thanks to Howard Tanner for a similar sug
I
believe this is the code that will put the focus on sheet
2
my $sheet = $Book->Worksheets("Sheet2").Activate
HTH
-John
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of
[EMAIL PROTECTED]Sent: Thursday, November 18, 2004 9:15
AMTo: [EM
> Date: Thu, 18 Nov 2004 17:14:54 -
> From: <[EMAIL PROTECTED]>
> Subject: Problem in running macro on the right excel sheet.
> To: <[EMAIL PROTECTED]>
> Message-ID:
> <[EMAIL PROTECTED]
> ukdy.domain1.systemhost.net>
>
> Content-Type: text/plain; charset="us-ascii"
>
On Thursday, November 18, 2004 2:23 PM, Craig Cardimon wrote
> Tie::File is great and it functions, but not if you don't want to
> change the source file. In my project, I have to create a new smaller
> document by extracting data from a larger original document. The
> original document, however,
Jason,
You are indeed slurping the whole file into memory with
the @logFile = construct. If you know your logs are big, and
you don't need to do arbitrary seeking around inside the file, don't do
it this way.
Line-based processing, as in...
open(LOGFILE,"
while() {
Craig Cardimon [cardimon AT knowledgeexpress DOT com] wrote:
>
> I, too, am working with some awfully huge text files, some of
> which are plain text and some of which are HTML tagged. Here's
> how I start:
>
> # I assign a filehandle to file
> open(IN, "$filename");
>
> # I 'slurp' in the file
$Bill Luebkert wrote:
That's because you didn't close $command before trying to delete
the temp files. DIR still has them open for write and unlike
UNIX, Doze can't delete files that are in use.
Thx Bill. (also thanks to Howard Tanner for a similar suggestion)
I understand what you'r
On Thu, 18 Nov 2004, Don Osburn wrote:
> I can not get ppm to install Audio-Wav. When I run
> ppm> describe Audio-Wav
> I get the following response.
>
> ==
> Name: Audio-Wav
> Version: 0.02
>Author: Nick Peskett
>
Title: RE: Working with very large text files
Additionally, I believe if you do:
$|=undef;
It sets the buffer to autoflush -- otherwise you may see your program processing the entire file before printing anything out, which could be frustrating. . .
As with setting any of these variables,
Tie::File is great and it functions, but not if you don't want to change
the source file. In my project, I have to create a new smaller document
by extracting data from a larger original document. The original
document, however, has to be left intact for future reference.
michael higgins wrote:
DePriest, Jason R. wrote:
> I have a perl script that I use to parse a month's worth of Cisco PIX
> Firewall logs sent to a syslog server.
>
> The raw text file is always over 300 MB and typically closer to 750 MB
> or higher.
>
> Opening a regular file handle (eg open(LOGFILE," beating the syst
DePriest, Jason R. wrote:
I have a perl script that I use to parse a month's worth of Cisco PIX
Firewall logs sent to a syslog server.
The raw text file is always over 300 MB and typically closer to 750 MB
or higher.
Opening a regular file handle (eg open(LOGFILE,"
It looked very much like perl was
[EMAIL PROTECTED] wrote:
> I have a perl script that I use to parse a month's worth of Cisco PIX
> Firewall logs sent to a syslog server.
>
> The raw text file is always over 300 MB and typically closer to 750 MB
> or higher.
>
> Opening a regular file handle (eg open(LOGFILE," beating the system
I, too, am working with some awfully huge text files, some of which are
plain text and some of which are HTML tagged. Here's how I start:
# I assign a filehandle to file
open(IN, "$filename");
# I 'slurp' in the file into one variable
{
local $/;
$wholefile = ;
}
# I close the fil
I have a perl script that I use to parse a month's worth of Cisco PIX
Firewall logs sent to a syslog server.
The raw text file is always over 300 MB and typically closer to 750 MB
or higher.
Opening a regular file handle (eg open(LOGFILE,";
close(LOGFILE);
did not help the memory usage either.
I can not get ppm to install Audio-Wav. When
I run
ppm> describe Audio-Wav
I get the following response.
==
Name: Audio-Wav
Version: 0.02
Author: Nick Peskett
Title:
Audio-Wav
Location: ActiveState Pac
See perldoc FileHandle. Methinks FileHandle is keeping the files open. Try
adding:
$command->close;
or
undef $command;
after instantiating the FileHandle. Either should close the files.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of colin_e
Sent: Thu
colin_e wrote:
> "$Bill Luebkert" wrote-
>
>
>>I'm not comvinced. You're probably doing something else wrong.
>
>
> Petr Vileta wrote-
>
>
>>Try:
>>unlink("\"C:/DOCUME~1/colin/LOCALS~1/Temp/Test_Schedule_1.000_OUT_3780.txt\"");
>
>
>
>
> You are right to be suspicious, but it's taken m
[EMAIL PROTECTED] wrote:
> Hi All,
>
> I'm trying to run a macro on an excel.
> There are several sheets in the excel (sheet1, sheet2, sheet3,..etc.)
> The excel is saved as its focus on sheet1.
> I try to run macro on sheet 2.
> So I write the code like this..
>
> use strict;
> use Win32::OLE qw
"$Bill Luebkert" wrote-
I'm not comvinced. You're probably doing something else wrong.
Petr Vileta wrote-
Try: unlink("\"C:/DOCUME~1/colin/LOCALS~1/Temp/Test_Schedule_1.000_OUT_3780.txt\"");
You are right to be suspicious, but it's taken me several hours of
head-scratching to nail this down. It's
Hi All,
I’m trying to run a macro on an excel.
There are several sheets in the excel (sheet1, sheet2,
sheet3,..etc.)
The excel is saved as its focus on sheet1.
I try to run macro on sheet 2.
So I write the code like this..
use strict;
use Win32::OLE qw(in with);
use Win32::
Petr Vileta wrote:
>>>Try:
>>>
>
> unlink("\"C:/DOCUME~1/colin/LOCALS~1/Temp/Test_Schedule_1.000_OUT_3780.txt\"
>
>>>");
>>
>>Shouldn't make any difference since there are no chars that need escaping.
>>
>>Try running this and post result :
>
> I'm not sure if Perl under Windows accept two dots
> > Try:
> >
unlink("\"C:/DOCUME~1/colin/LOCALS~1/Temp/Test_Schedule_1.000_OUT_3780.txt\"
> > ");
>
> Shouldn't make any difference since there are no chars that need escaping.
>
> Try running this and post result :
I'm not sure if Perl under Windows accept two dots in filename in unlink()
function
Petr Vileta wrote:
>>However I've hit a weird problem on ActiveState perl 5.8.3 on XP. If I
>>put temp files in
>>the default Windows personal temp directory, I end up with pathnames like-
>>
>>C:/DOCUME~1/colin/LOCALS~1/Temp/Test_Schedule_1.000_OUT_3780.txt
>>
>>Now I can create this path
> However I've hit a weird problem on ActiveState perl 5.8.3 on XP. If I
> put temp files in
> the default Windows personal temp directory, I end up with pathnames like-
>
> C:/DOCUME~1/colin/LOCALS~1/Temp/Test_Schedule_1.000_OUT_3780.txt
>
> Now I can create this pathname quite happily wit
colin_e wrote:
> Perl: v5.8.3 MSWin32-x86-multi-thread
> OS: Windows XP SP1
>
>
> Solaris is my production platform, but I mostly develop on my home PC
> for convenience.
> Perl's cross-platform compatibility is generally very good, but i've hit
> an odd path problem-
>
> Although the Windows
Perl: v5.8.3 MSWin32-x86-multi-thread
OS: Windows XP SP1
Solaris is my production platform, but I mostly develop on my home PC
for convenience.
Perl's cross-platform compatibility is generally very good, but i've hit
an odd path problem-
Although the Windows command shells use "\" as a path sepa
27 matches
Mail list logo
