At Fixya.com, our trusted experts are meticulously vetted and possess extensive experience in their respective fields. Backed by a community of knowledgeable professionals, our platform ensures that the solutions provided are thoroughly researched and validated.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
1. use the lowest power eyepiece (highest number in mm) 2. Point the scope towards a object (about 1000yds) away during the day and see if you can focus on the object. If you can not see anything during the day there is a problem either with the scope or set-up 3. Align the finder to the daylight object so it is ready for night viewing. 4. First night object should be the moon. Easy to find. ( A full moon presents poor seeing but this is just to get used to the scope. 5. Once the above steps are completed, use a good star program to find interesting objects (Stellarium, Cartes du Soliel, C2A are all freeware) 6. If you can not see the daytime object, remove the eyepiece and look down the focus tube. You should see a reflection of your eye in the primary mirror. If not, the primary and/or secondary mirror need to be collimated (aligned) refer to your owners manual.
Hello,
The standard way of creating a database using VBA, which can be modified to suit your needs is this-->
Note: the code (wspDefault.CreateDatabase("Newdb.mdb"...), can bealtered to save the database in a folder such as "C:\NEWDB\text.mdb".sub NewDatabase()
Dim wspDefault As Workspace, dbs As Database
Dim tdf As TableDef, fld1 As Field, fld2 As Field
Dim idx As Index, fldIndex As Field
Set wspDefault = DBEngine.Workspaces(0)
' Create new, encrypted database.
Set dbs = wspDefault.CreateDatabase("Newdb.mdb", _
dbLangGeneral, dbEncrypt)
' Create new table with two fields.
Set tdf = dbs.CreateTableDef("Contacts")
Set fld1 = tdf.CreateField("ContactID", dbLong)
fld1.Attributes = fld1.Attributes + dbAutoIncrField
Set fld2 = tdf.CreateField("ContactName", dbText, 50)
' Append fields.
tdf.Fields.Append fld1
tdf.Fields.Append fld2
' Create primary key index.
Set idx = tdf.CreateIndex("PrimaryKey")
Set fldIndex = idx.CreateField("ContactID", dbLong)
' Append index fields.
idx.Fields.Append fldIndex
' Set Primary property.
idx.Primary = True
' Append index.
tdf.Indexes.Append idx
' Append TableDef object.
dbs.TableDefs.Append tdf
dbs.TableDefs.Refresh
Set dbs = Nothing
End Sub Hope this helps! Please let me know if you have any questions.Thank You,Raph30
I'm assuming that you're using Business Objects full client, in which case we can simply reset your user preferences.
Workflow on your machine
1. Start > Run > Type Regedit -- this will bring up your registry 2. Browse to:
HKEY_CURRENT_USER\Software\Business Objects\Suite 11.5\default\BusinessObjects\ "username" user prefs
3. Delete only the key that shows your username 4. Note - the above registry path is for BO XIR2, for version 6 the version name will be slightly different.
Log back into Business Objects and rerun the report.
If changes have been made to the universe it may well be that in Deski you're using a local copy of it, I would first advise exporting the universe to the repository (cms ) and having another go in Infoview just to ensure that the same copy of the universe is being used.
If it still fails, you will need access to the Business Objects server as it could well be that the connection on the server is either missing, incorrect or using a different version of middleware.
The fastest way to check on the server, is to launch Deski directly on the server and import the report > refresh it and see if you get the error. If so then we know that it's a connectivity issue.
×