Re: DB Result Wizard Error

Hi,

No these are not the true field names. i.e. Equipment serial number is
EqSerNum, ModelNum, CCCode etc... I went through all that to ensure that
there were no spaces in any of the field names in all the tables.

"Ronx" wrote:

> "Equipment Serial Number, Equipment Model Number, Cost Accounting
> Code, etc..."
>
> Are the above table or field names? If so, they should not contain
> spaces, or the names should be wrapped in square brackets in your
> query.
> [Equipment Serial Number], [Equipment Model Number], [Cost Accounting
> Code], etc...
> When using the FP wizards it's easier to remove the spaces from the
> table/field names.
>
> --
> Ron Symonds
> Microsoft MVP (FrontPage)
> Reply only to group - emails will be deleted unread.
>
>
> "GSR" <GSR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:1087FE1F-42B6-45C1-A11A-17170D60F1FF@xxxxxxxxxxxxxxxx
> > Hi,
> >
> > It is the standard message: "Database Results Wizard Error
> > The operation failed. If this continues, please contact your server
> > administrator."
> >
> > Searched MS and reviewed / tried the solutions provided that
> > appeared to be
> > relevant. Reviewed even those that provide additonal error
> > information.
> >
> > Most of the pages created are straight forward and do not contain
> > any
> > additional code, and in most cases nothing more than changing the
> > font size
> > and adding appropriate headings, colors etc...
> >
> > As for the structure of the tables, these are simple tables (i.e.
> > EmplyLName, EmplyFName, ID, etc...) In short the tables are very
> > generic and
> > the names do not mathc any reserved wording, and contain no specific
> > formatting requirements, in short, these are standard text fields...
> >
> > The queries used are also simple. For instance, most contain five
> > or less
> > fields and are used only for display purposes and do not contain any
> > linked
> > tables, i.e. table 1 and table 2 (linked), which is used to create
> > query X.
> > For instance Equipment Serial Number, Equipment Model Number, Cost
> > Accounting
> > Code, etc...
> >
> > The actual change made was to the equipment inventory query, which
> > was used
> > to display the new equipment information. In this case, the
> > hostname, which
> > is in the table was added to the query. The quary was regenerated
> > with no
> > errors. This query is used for displaying information. There are
> > not
> > buttons on the form, no hyperlinks to retrieve associated records
> > etc...
> >
> > Went to a metting, and hour later... opened the site to complete and
> > initial
> > review of the pages... This is when the error appeared... Closed
> > MSIE...
> > opened the site and found nothing out of the ordinary. No one else
> > had been
> > in the site except myself... Spent half the day trying to identify
> > what went
> > wrong... Spent the other half trying to regenerate a few of the
> > pages...
> > eventually, leading to the original post... the following day...
> >
> > Thanks,
> > Greg
> >
> >
> >
> >
> >
> >
> > "Stefan B Rusynko" wrote:
> >
> >> What is the specific error
> >>
> >> --
> >>
> >> _____________________________________________
> >> SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
> >> "Warning - Using the F1 Key will not break anything!" (-;
> >> To find the best Newsgroup for FrontPage support see:
> >> http://www.net-sites.com/sitebuilder/newsgroups.asp
> >> _____________________________________________
> >>
> >>
> >> "GSR" <GSR@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:97B05DFD-1506-4955-8849-41088968E6F4@xxxxxxxxxxxxxxxx
> >> | Create sub site on extranet site. Created MS Access DB and
> >> completed import.
> >> | Used the DIW to create the base pages and completed the necessary
> >> edits.
> >> | Something went wrong and so the site was removed and reinitiated
> >> to include
> >> | regenerating all the pages. Made a change to include one
> >> additional field
> >> | for display so that link to open and edit page could be
> >> completed. I've this
> >> | several time with no issues. However, without fail the error DRW
> >> appears.
> >> | Only this time every blasted page provided this same error and I
> >> did not even
> >> | revise / open. This seems to be a consistent problem and the KB
> >> does not
> >> | list anything significant that appears to resolve the problem.
> >> |
> >> | There are no reserved words in use, each query has been checked
> >> and
> >> | rechecked. Each table has been checked and even redfined etc...
> >> I even
> >> | create the tables using the feature within and still get the same
> >> issue...
> >> | FP reinstall etc... Same issue...
> >> |
> >> | I need some guidance on how this can be resolved without
> >> recreating
> >> | everything for a fourth time. I thought the first or second time
> >> might have
> >> | been something but this is number four in seven days... and
> >> frankly this is
> >> | becoming old...
> >> |
> >> | Can someone please give me an idea of what is going on????
> >>
> >>
> >>
>
>
>
.