Table 3.05 - Application Error .... Memory could not be written...

[bcr...@adobeforums.com]

Running PageMaker 7.01a with Table 3.05 on Windows2000 SP4. When I try to close Table 3.05 after opening up a table inside PageMaker the Table program crashes.

Error message: Adobe Table 3.0: TABLE30.EXE - Application Error
The instruction at "0x00483f80" referenced memory at "0x33e8658f". The memory could not be "read".

I get another appliction error after clicking OK.

The Table gets updated inside PageMaker, but if I try to double-click the table to open it back up I get another error message.

"Cannot use OLE object
Pagemaker cannot start the server application. Make sure there is enough memory and that the server is installed properly."

It will also crash instantly by simply launching Table 3.05 by itself and trying to copy <CTRL>-<C> all the cells.

This previously worked fine, but I've been away from PageMaker for a few months because I've been working on other things. PageMaker is also loaded on a few other computers in the office with users who don't are not using Table. Table crashes on theirs too. The only thing I can think of is the workstations here get automatically updated over the internet. Maybe one of the updates broke it.

[Bob_Levine]

Do not use insert object. Create an EPS from Table and use file>place.

See the FAQs for the dangers of OLE and proper graphic file formats.

Bob

[B_Ro...@adobeforums.com]

That is not acceptable. I'm creating a catalog that has nothing but huge tables on every page and the catalog itself is several hundred pages. I'm not going to insert my tables as graphics. In order to go back and edit that table I would either have to recreate the entire table or save hundreds of tables for all the pages. Adobe Table previously worked, I'm trying to find out why it stopped working.

Adobe Table not only crashes in PageMaker. It will crash if you put a table inside Excel and try to update it as well. As I mentioned before, Adobe Table will also crash all by itself. All you have to do is open Adobe Table and highlight all the cells and try to copy them using the copy command.

[John_...@adobeforums.com]

Hi, B,

Donald Gruener "4.5 - Adobe Table recommendations" 5/7/02 9:06am </cgi-bin/webx?14@@.ef861df/0>

> Adobe Table previously worked, I'm trying to find out why it stopped
working.

That is the problem with OLE/Paste Special - it is unstable.

OLE is highly problematic in the Postscript environment (e.g. creating PDFs), severely restricts portability (other applications have to be present) and is really only present in PageMaker to gain Microsoft approval as a Windows application. It has been dispensed with in newer applications, e.g. InDesign.

InDesign <http://www.adobeforums.com/cgi-bin/webx?14@@.ef861f6/0> will import Excel files directly, and they can be eidted directly in InDesign. This may be a better option if you have publications with many tables.

Iechyd da! John
22:09 04/08/2004 BST

[Peter_...@adobeforums.com]

As I mentioned before, Adobe Table will also crash all by itself. All you have to do is open Adobe Table and highlight all the cells and try to copy them using the copy command.

You're right about that. I found that out the hard way. My workaround: copy all but one cell, then come back for that one leftover cell.

In order to edit tables, launch TE& from there open tables as required. If u alt-dbl clk from within pm, you will have a headache!

[Bob_Levine]

> That is not acceptable.

Then why did you ask for advice? Nothing irks more than people ask for
advice and when it's given they blow it off.

Have fun doing it your way, I'm bowing out of this thread.

Bob

[B_Ro...@adobeforums.com]

"Then why did you ask for advice? Nothing irks more than people ask for
advice and when it's given they blow it off."

I appreciate the offer for an alternative solution, but that alternative is unreasonable. I need a solution to the actual problem, not a bandaid.

"InDesign will import Excel files directly, and they can be eidted directly in InDesign. This may be a better option if you have publications with many tables. "

I tried InDesign. It would be a better product and does an "OK" job at importing PageMaker 7, but my company just purchased 3 copies of PageMaker last year. I'm not sure they would go for 3 upgrades at $350/seat.

The 3rd workstation still works fine and has all the MS Windows updates. So that rules out the updates breaking Adobe Table. ReInstalling PageMaker/Table doesn't fix the problem either. This is very odd... Adobe Table worked fine and I used it for 6 months numerous times a week without any problems. All 3 workstations are running Windows2000 SP4.

[Lyn_Eg...@adobeforums.com]

B Rogers:

You might not find the solutions offered (or rather, lack of the one you wanted to hear) as acceptable, but the forum regulars can only advise using their collective wisdom. And so many times, people have posted questions about Adobe Table - "it always worked fine and all of a sudden it's not" - and the answer is always the same. Dont use it. You've been lucky if it worked in the past, but there is no workaround that is reliable other than that sugggested.

I just did a search for 'Adobe Table' on this forum, and apart from the FAQ which directly addresses it, the following threads - all with the same problem as you and all given the same answer - appeared on the first two pages of results:

Donald Gruener "4.5 - Adobe Table recommendations" 5/7/02 9:06am </cgi-bin/webx?13@@.ef861df/0>

barbararohrs "Place an Adobe table in Pagemaker" 7/27/04 12:50pm </cgi-bin/webx?13@@.3bb4b8f8/16>

Robert Levine "Strange Printing of Adobe Tables" 7/20/04 6:16am </cgi-bin/webx?13@@.3bb50f9b/2>

Lyn Eggleston "Multi-Page Tables" 6/30/04 12:55am </cgi-bin/webx?13@@.3bb4d0b4/7>

Ian Matthew "Place an Adobe table in Pagemaker" 6/27/04 4:39am </cgi-bin/webx?13@@.3bb4b8f8/6>

KelliA "Adobe Table Exporting Problem" 6/10/04 9:04am </cgi-bin/webx?13@@.3bb3efba/20>

Robert Levine "Error "Cannot Flush the Volume" at Adobe Table" 5/25/04 2:11pm </cgi-bin/webx?13@@.3bb448ee/0>

Robert Levine "Windows XP and Adobe Table" 5/10/04 11:37am </cgi-bin/webx?13@@.2cd0cfc8/16>

[B_Ro...@adobeforums.com]

Once again I appreciate everyones help. I solved the problem. The problem was related to something in my windows profile. Your profile stores windows settings, internet settings, my documents, and most importantly registry entries pertaining to that users login. Here is a small writeup I created in case anyone else runs into this problem. Keep in mind that if you don't know what your doing with handling the windows profile you could potentially lose your settings, internet favorites, documents, email, etc. You will need local admin privleges to your workstation to perform this.

Note: If your using a roaming profile make sure you change your windows settings to a local profile under your normal login before you start this step by step solution. When you are through you can switch back to the roaming profile and sync up with the server.

1. Login as another different user with local admin priveledges. If you don't know another login then create one with local admin priveledges.

2. Move the folder containing your profile of your normal login to a safe place outside of the "Documents and Settings" folder. This will be used later on to restore your profile. Make sure you move it and not copy/paste it.

3. Login under your normal username. Windows will now create a new profile.

4. Windows will more than likely look different at this point unless your the kind of person that doesn't personalize your desktop. This is where you will start copying your documents, settings, email, from your original profile that you moved out into your new profile.

5. At this point Adobe Table will no longer crash, but it will prompt you to save your table as a PDF when try to copy it or edit it inside PageMaker.

6. ReInstall Acrobat Distiller to fix the "save as PDF" problem.

7. That's it! Problem solved. :)

[John_...@adobeforums.com]

Hi, B,

So let me get this straight:

You are saying that the cause of Table Editor crashing is a corrupt User profile, and that with a new (admin) user profile Table Editor works correctly?

Can you give any more detail - like why and exactly which part of the profile is the key area?

Iechyd da! John
21:38 05/08/2004 BST

[Lyn_Eg...@adobeforums.com]

Ooops. I meant to say 'unacceptable'.

[B_Ro...@adobeforums.com]

Yes, a new user profile alleviated the problem of Adobe Table crashing when:

* You try to copy the entire table. -or-
* Trying to close Adobe Table after double-clicking it inside PageMaker.

I'm not sure exactly which part of the profile was causing Adobe Table to crash. There is Adobe information stored under the "Application Data" folder, but I think it was related to something in the user registry. All the users profile registry entries are stored in file called NTUSER.DAT in the root of the users profile folder. I didn't copy this file from the old profile to the new one.

If you think this solution might solve your problem then just create a new local user and login. Launch Adobe Table and see if the copy command crashes AT when you highlight all the cells. If it doesn't crash and prompts you to save the file as PDF then the solution above will solve your problem.

[B_Ro...@adobeforums.com]

I have more information and narrowed the problem down. Creating a new profile may not fix this problem. The problem is related to the default printer that is selected. Creating a new profile on my computer fixed the problem because the new profile selected uses a different default printer. For some reason when I select the HP LaserJet 2100 as my default printer, Adobe Table starts crashing when I do the operations described above. I just recently setup this printer on my local computer through the network. Changing the driver on the computer hosting the printer to a PCL5 driver that comes standard with Windows2000 solved the problem completely.

[John_...@adobeforums.com]

Hi, B,

> Changing the driver on the computer hosting the printer to a PCL5 driver
that comes standard with Windows2000 solved the problem completely.

I'm a bit confused as to what you're proposing as the solution - creating a new user profile, changing the system default printer to PCL or both.

I'm not surprised that OLE works with a PCL printer as that's what Microsoft probably prefer. But it doesn't offer much help to those who are working in Postscript mode.

Iechyd da! John
11:44 21/08/2004 BST

[Bob_Levine]

That's your second solution. Come on back when that falls apart, too.
Because it will.

Bob

[B_Ro...@adobeforums.com]

John, sorry didn't mean to confuse things. The reason creating a new profile solved the problem initially was because on my workstation the default printer was set to different printer. After I changed the printer back to the LaserJet 2100 I started having problems again. Changing the printer driver to the PCL5 driver supplied with Windows2000 solved the problem with Adobe Table crashing. There is no need to create a new users profile.

Does Adobe Table crash in the way I described above using a postscript driver?

Bob,
I have no idea why you have such a negative attitude towards me. I came back because I narrowed down what the exact problem was. At least if someone runs into the same problem that I did they will have an alternate solution.

[John_...@adobeforums.com]

Hi, B,

First of all, TE generally works fine on Win2K as an independent app. For some reason getting TE to work on WinXP is far more problematic and there are many user messages here to confirm that.

Secondly, OLE is not recommended as part of PM's workflow, and if it's going to work at all with PM, the "Compose To" and default printers need to be PCL.

Thirdly, the recommended way to import TE Tables into PM is to export the Table in EPS format and then place it into PM.

Full details in FAQ: Donald Gruener "4.5 - Adobe Table recommendations" 5/7/02 9:06am </cgi-bin/webx?14@@.ef861df/0>

I'm pleased you've got TE working.

Iechyd da! John
20:40 23/08/2004 BST

[Bob_Levine]

I don't have a negative attitude towards you. But I don't want lurkers
thinking that you've come up with some miracle cure that nobody else
has. OLE simply doesn't work consistantly in a postscript workflow.
While I'm happy for you that you've got it working now, I can assure you
that it's just a matter of time before this workflow bites you again.

If you're using a workflow that requires heavy use of tables you should
be looking at InDesign.

Bob

[Stu_...@adobeforums.com]

But I don't want lurkers thinking that you've come up with some miracle
cure that nobody else has.

But maybe, just maybe, he's come up with a solution that will help some lurkers get their work out.

OLE simply doesn't work consistantly in a postscript workflow.

But if he's using PCL printers, then it's not really a postscript workflow, now, is it?

While I'm happy for you that you've got it working now, I can assure you
that it's just a matter of time before this workflow bites you again.

And, given the evidence so far, just a bit more time before he figures out why and solves the problem.

If you're using a workflow that requires heavy use of tables you should
be looking at InDesign.

On that we agree. But earlier in the thread he said that his company was one of those that's been reeled in by Adobe's continuing to market an obsolete application with no warning to the unwary that they're buying into a dead end.

[Bob_Levine]

Stu,

Would you bet your mortgage on his workflow or mine? <g>

Bob

[Jo...@adobeforums.com]

>
> ... his company was one of those that's been reeled in by Adobe's

continuing to market an obsolete application with no warning to the unwary
that they're buying into a dead end.

I've read a couple of those stories here lately, and I'm not sure why. In
the fall of '01 I went shopping for an upgrade to PM, or a determination
that we should stick with 6.52. It didn't take long to realize that PM was
last century, and ID is this century. What's happened this year was
*clearly* evident back then..PM is a relic.

To these folks I say...do your #^@(#*+^# homework!!!

Stu: I agree, but until PM causes some manager or director to look bad at
Adobe, nothing will change.

-John O

[Stu_...@adobeforums.com]

Would you bet your mortgage on his workflow or mine?

Neither ;-)

[John_...@adobeforums.com]

Hi, B,

Don't forget that creating a PDF requires the use of the Postscript Printer Driver.

Iechyd da! John
17:23 24/08/2004 BST

[B_Ro...@adobeforums.com]

I wish I would have done more research on desktop publishing software, but I was working primarily on other projects. I'm a mechanical engineer who is trying to bring a company’s catalog out of the dark ages. I'm sure everyone would get a good chuckle if they could see the catalog and all the inconsistencies in the format/layout. Creating this catalog in PageMaker is huge step forward despite all of PageMaker's deficiencies.

For those that are using postscript you will have to stick with what Bob and the others have suggested. I have very little technical background in desktop publishing and postscript environments. I'm just very stubborn and persistent when it comes to flakey software that stops working after dumping enormous amounts of time into it.

I haven't tried printing to a postscript printer so I have yet to see the problems that some of you are having. The graphic images I'm using in the catalog are raster images so PCL is fine with me for the time being. I have Windows XP at home and may do some experimenting with using Adobe Table and printing to a postscript printer. Please don't expect any earth shattering breakthroughs. The problems that some of you are having are very old. I'm sure there are a lot of users who spent ludicrous amounts of time trying to fix it. Think of it as me sharing the pain that you guys are going through.

For those that don't need postscript, running Windows 2000, unfortunate enough to have PageMaker, and plan on using Adobe Table I hope they find my information useful.