Prev: Links in outlook express 6
Next: Database for a Testing Center - Tracking dates
From: Scott Shearer on 1 Jun 2010 14:14
There were no errors when publishing. In addition, I can see the form and
lists that were created form within SharePoint. The only issue that I have
is that the form will not display.

Also, I was running the SharePoint 2010 beta and the Office 2010 beta with
no issues. I unistalled the beta versions, installed the RTM versions and am
now experiencing this issuee.

"Albert D. Kallal" wrote:

> Since no forms seem to render on the web, but they do publish, then often
> this comes down to permissions.
>
> For example, I use the IP address such as:
>
> 192.168.1.15/combotest/default.aspx
>
> I can get to the basic SharePoint site and browse objects.
>
> However, if I attemp to pblish or launch access web forms, they fail.
>
> If I use the full server name, such as:
>
> http://win-16xrrnvkz0t/combotest/default.aspx
>
> I have not quite figured out why I can't use the IP address url (the rest of
> the site works). However, when I use the 2nd url, both publishing and
> viewing of forms works fine. There some authentication issue here I not
> quite figured out yet.
>
> However, when you view all objects you publish, (view the objects and
> settings), you should see something like:
>
> http://cid-b18a57cb5f6af0fa.skydrive.live.com/self.aspx/.Public/AccessHelp/sp1.png?sa=22284429
>
> Note in the above, some forms did not publish due to problems.
>
> When you list the objects on the web site, do your forms show up as above?
>
> The above shows that you don't necessary need to setup a startup form here.
> You can really just launch/view any form from the above list in the the
> above screen shot.
>
>
> --
> Albert D. Kallal (Access MVP)
> Edmonton, Alberta Canada
> pleaseNOOSpamKallal(a)msn.com
>
From: Scott Shearer on 1 Jun 2010 14:25
There were no errors in publishing the form and all looks normal from within
SharePoint. I did not set a startup form, so the "Settings" screen displays
when I access the site. When I try to view the published form, I get an
error.

"Albert D. Kallal" wrote:

>
> "Roger Carlson" <RogerCarlson(a)noemail.noemail> wrote in message
> news:ODVuolaALHA.584(a)TK2MSFTNGP02.phx.gbl...
> > You mean you're trying to access the form in SharePoint? My advice is
> > don't. All changes should be made in the Access client. The Microsoft
> > development team has a saying with regards to web applications:
> > "Everything begins and ends with Access client."
> >
> > --
>
> The above is so very correct, but the issues were really only a problem
> during beta.
>
> If you actually do choose the "modify" form option, it requires and launches
> the access client for you to make the modifications. So, one does not have a
> choice, the client is launched.
>
> However, in this case the user is just trying to launch the web form, not
> actually modify it.
>
> During during development I now often don't setup a "start up" form in
> Access for the web site. Thus one can simple "view" the object list of
> forms, reports etc in SharePoint. This view is much like the view of objects
> in the access client. From that list, any web object can be launched to run
> inside of a web browser. So, this saves having to launch the main navigation
> form, and then navigate through the application to finally get to the
> particular form in question.
>
> So, my browser sits on this URL and I hit f5 after I publish to see the
> updated list of objects. I can also click on any object (forms, reports). to
> launch it in the web browser.
>
> I also use the above view for debugging. Forms can often pass compatibility
> for the web, but when published their code does not compile server side. The
> screen here shows this case:
>
> http://cid-b18a57cb5f6af0fa.skydrive.live.com/self.aspx/.Public/AccessHelp/sp1.png
>
> So, I pretty much keep the above web screen up and running all the time
> during development.
>
> In the above you can see that two web forms published to the web, but some
> code inside failed compiling web side and thus the "Creating Fail" message.
> I have to write up an article as how I then start the process to find/fix
> the errors in those bad forms..
>
> I have to say, I really starting to enjoy this new Web toy called Access...
>
> --
> Albert D. Kallal (Access MVP)
> Edmonton, Alberta Canada
> pleaseNOOSpamKallal(a)msn.com
>
>
> .
>
First  |  Prev  | 
Pages: 1 2
Prev: Links in outlook express 6
Next: Database for a Testing Center - Tracking dates